• People

• Goals

• Developers

• Login

• Documentation

• Credits

• Machines

• Resources

• Portal Master

• Project Master

• Web Master

1. Send an email to ASC_code_master@wugrav.wustl.edu specifying which arrangements you would like to access. You will receive a userid and password.
   
   
2. Login to the pserver: enter the command
   
   cvs -d :pserver:cvs_user@wurel.wustl.edu:/cvsroot login
   
   where cvs_user is the userid assigned to you. At the prompt, enter your password.
   
   
3. The available modules may be listed via
   
   cvs -d :pserver:cvs_user@wurel.wustl.edu:/cvsroot checkout -s
   
   
4. To check out a given module `module-name' use
   
   cvs -d :pserver:cvs_user@wurel.wustl.edu:/cvsroot checkout module-name
   
   for example,
   
   cvs -d :pserver:cvs_user@wurel.wustl.edu:/cvsroot checkout GRAstro_Hydro

The codes we develop in the Astrophysics Simulation Collaboratory Project are for the whole community. You are encouraged to download and make full use of these codes. In using these codes, we ask you to:

1. Send a message to ASC_code_master@wugrav.wustl.edu providing a brief description (a couple of sentences) of what you are planning on doing with the code. This is useful for letting us know who is doing what with the codes and in helping us to write reports to the funding agencies of the project.
   
   
2. If you publish results that in some way benefited from the code you obtained in this repository, either from direct application of the code, from using some part of it, or from having learned something from it, please acknowledge the use accordingly. (We need your acknowledgment to get funding to continue our effort!) We suggest you acknowledge both the ASC project and the individual author(s)/contributor(s) of the major code modules that you have used, e.g., "the work benefits from using the ASC codes developed in the ASC project, in particular the modules xxx written by xxx and xxx by xxx. (No need to acknowledge all modules and all authors, but it would be good to acknowledge the major ones. In this way we hope the authors/contributors as individuals in the project will get the credit they deserve.)

We also hope that you will help us (and the community) to further develop these codes, and keep a free flow of information. In this regards, please:

1. Let us know if you find bugs, encounter difficulties, think of good features to add, or make wonderful progress (please email the authors of the codes, cc-ing ASC_code_master@wugrav.wustl.edu). Although we presently do not have a dedicated person for code support (all authors/contributors of our codes are research physicists or computer scientists who are under pressure to push their own part of the research project), and cannot guarantee that the bugs/features you report/request will be taken care of in a short time, we will surely try our best in making the usage of the code as productive as possible for everyone.
   
   
2. Often in using the ASC codes you will find that adding some features, e.g., a new finite differencing treatment in solving the spacetime or hydro equations, is useful to your research. We encourage you to code these features up in the form of a new module, and add them to the ASC repository. Most application codes in the ASC repository are based on the Cactus computational toolkit (http://www.cactuscode.org), which specifically allow modules (thorns) carrying new features to be added in a convenient and consistent fashion. Please send your contribution to ASC_code_master@wugrav.wustl.edu, and your contribution will be added to and acknowledged in the repository. We encourage you to apply existing testsuites and supply additional testsuites for your contribution. If you need modifications/hooks to be added to the existing codes for your new thorn, please inform the original authors of the relevant codes, cc-ing ASC_code_master@wugrav.wustl.edu. We will try to do our best to incorporate your contribution and support it as part the ASC collection (you as an author/contributor of that code will be credited and be responsible for the bugs in it as all others who have contributed to the project).