... | ... | @@ -15,25 +15,28 @@ The *print citation* command will print the correct citation for the version you |
|
|
|
|
|
# Setting up this version
|
|
|
|
|
|
1. DownLoad the code, data, and documentation. This creates several directories, Each contains a readme.htm file describing the contents of that directory.
|
|
|
1. [DownLoad](DownLoad) the code, data, and documentation. This creates several directories, Each contains a readme file describing the contents of that directory.
|
|
|
|
|
|
2. EditPath - instructions for how to specify where the data files are located. *Important! * The code will not run if it cannot find the data files.
|
|
|
2. [EditPath](EditPath) - instructions for how to specify where the data files are located. *Important! * The code will not run if it cannot find the data files.
|
|
|
*Important and convenient! * This will be done for you if you use our makefile.
|
|
|
|
|
|
3. CompileCode - how to compile the code using a variety of compilers.
|
|
|
3. [CompileCode](CompileCode) - how to compile the code using a variety of compilers.
|
|
|
|
|
|
4. RunSmokeTest - check that the code works.
|
|
|
4. [RunSmokeTest](RunSmokeTest) - check that the code works.
|
|
|
|
|
|
5. RunCode - This explains how to execute the code.
|
|
|
5. [RunCode](RunCode) - This explains how to execute the code.
|
|
|
|
|
|
6. MpiParallel describes how to use the optimize and grid commands on a parallel cluster, using either MPI or a makefile.
|
|
|
6. [MpiParallel](MpiParallel) describes how to use the optimize and grid commands on a parallel cluster, using either MPI or a makefile.
|
|
|
|
|
|
7. CompileStars - You must compile some stellar data files if you want to use the some of the table star command to include realistic stellar continua.
|
|
|
7. [CompileStars](CompileStars) - You must compile some stellar data files if you want to
|
|
|
use the table star command to include realistic stellar continua.
|
|
|
|
|
|
8. TestSuite is a large number of test cases that you should run to confirm that all is well. This is a critical step since it will check for bugs in your compiler. That directory also contains a group of programs that show how to call the code as a subroutine.
|
|
|
8. [TestSuite](TestSuite) is a large number of test cases that you should run to confirm that all is well. This is a critical step since it will check for bugs in your compiler. That directory also contains a group of programs that show how to call the code as a subroutine.
|
|
|
|
|
|
9. HotFixes are a set of corrections to the source. These will be incorporated in the next incremental upgrade, are listed in the HotFixes page. It is *_very important*_ that you edit the source to incorporate these hot fixes since they correct known problems. The source you obtain here *_does not have any*_ of these these fixes included. (Reason: this is the source that created the output files that are downloaded with the test suite. You can validate your system/compiler by confirming that this source reproduces that output. This source and output constitute a reference for where the code was at a particular time.)
|
|
|
9. [HotFixes](HotFixes) are a set of corrections to the source. These will be incorporated in the next incremental upgrade, are listed in the HotFixes page. It is *_very important*_ that you edit the source to incorporate these hotfixes since they correct known problems. The source you obtain here *_does not have any*_ of these fixes included. (Reason: this is the source that created the output files that are downloaded with the test suite. You can validate your system/compiler by confirming that this source reproduces that output. This source and output constitute a reference for where the code was at a particular time.)
|
|
|
|
|
|
10. KnownProblems are described on this page. The RevisionHistory page lists major changes to the code.
|
|
|
10. [KnownProblems](KnownProblems) are described on this page.
|
|
|
The [RevisionHistory](RevisionHistory) page lists major changes to the code.
|
|
|
|
|
|
-----
|
|
|
|
... | ... | |