Changes between Version 38 and Version 39 of StepByStep


Ignore:
Timestamp:
2012-11-05T14:09:18Z (7 years ago)
Author:
Gary J. Ferland
Comment:

formatting

Legend:

Unmodified
Added
Removed
Modified
  • StepByStep

    v38 v39  
    1010= Setting up this version =
    1111
    12  1. DownLoad the code, data, and documentation. This creates several directories,  Each contains a readme.htm file describing the contents of that directory.
     121. DownLoad the code, data, and documentation. This creates several directories,  Each contains a readme.htm file describing the contents of that directory.
    1313
    14  1. 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.
     142. 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.
    1515
    16  1. CompileCode - how to compile the code using a variety of compilers.
     163. CompileCode - how to compile the code using a variety of compilers.
    1717
    18  1. RunSmokeTest - check that the code works.
     184. RunSmokeTest - check that the code works.
    1919
    20 4. RunCode - This explains how to execute the code.
     205. RunCode - This explains how to execute the code.
    2121
    22 5. MpiParallel describes how to use the optimize and grid commands on a parallel cluster, using either MPI or a makefile.
     226. MpiParallel describes how to use the optimize and grid commands on a parallel cluster, using either MPI or a makefile.
    2323
    24 6. 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.
     247. 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.
    2525
    26 7. 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.
     268. 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.
    2727
    28 8. 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.)
     289. 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.)
    2929
    30 9. KnownProblems are described on this page.  The RevisionHistory page lists major changes to the code.
     3010. KnownProblems are described on this page.  The RevisionHistory page lists major changes to the code.
    3131
    3232-----