Heracles 4.0 User's Guide: Difference between revisions

No edit summary
No edit summary
Line 9: Line 9:
   cvs co -r  ''TAGNAME'' -d ''DIRECTORY''  GEOSagcm
   cvs co -r  ''TAGNAME'' -d ''DIRECTORY''  GEOSagcm


where ''TAGNAME'' is the model "tag" (version).  A tag in <code>cvs</code> marks the various versions of the source files in the repository that together make up a particular version of the model.  A sample release tag is <code>Ganymed-4_1</code>, indicating the latest patch of version Heracles 4.0 for general use. ''DIRECTORY'' is the directory that the source code tree will be created.  If you are using a stock model tag it is reasonable to name the directory the same as the tag.  This directory determines which model in presumably your space a particular experiment is using.  Some scripts use the environment variable <code>ESMADIR</code>, which should be set to the absolute (full) pathname of this directory.
where ''TAGNAME'' is the model "tag" (version).  A tag in <code>cvs</code> marks the various versions of the source files in the repository that together make up a particular version of the model.  A sample release tag is <code>Heracles-4_0</code>, indicating the latest patch of version Heracles 4.0 for general use. ''DIRECTORY'' is the directory that the source code tree will be created.  If you are using a stock model tag it is reasonable to name the directory the same as the tag.  This directory determines which model in presumably your space a particular experiment is using.  Some scripts use the environment variable <code>ESMADIR</code>, which should be set to the absolute (full) pathname of this directory.


When a modified version of some component of the model is saved to the repository, the tag it uses -- different from the standard model tag -- is supposed to be applied at most only to the directories with modified files.  This means that if you need to use some variant tag of a gridded component, you will have to <code>cd</code> to that directory and update to the variant tag.  So, for example, if you needed to apply updates to the SatSim gridded component, you would have to <code>cd</code> several levels down to the directory <code>GEOSsatsim_GridComp</code> and run  
When a modified version of some component of the model is saved to the repository, the tag it uses -- different from the standard model tag -- is supposed to be applied at most only to the directories with modified files.  This means that if you need to use some variant tag of a gridded component, you will have to <code>cd</code> to that directory and update to the variant tag.  So, for example, if you needed to apply updates to the SatSim gridded component, you would have to <code>cd</code> several levels down to the directory <code>GEOSsatsim_GridComp</code> and run  
Line 130: Line 130:
Hit ENTER to use Default Location:
Hit ENTER to use Default Location:
----------------------------------
----------------------------------
Default:  /discover/nobackup/aeichman/Ganymed-4_1
Default:  /discover/nobackup/aeichman/Heracles-4_0
</pre>
</pre>


Line 173: Line 173:
The following executable has been placed in your Experiment Directory:
The following executable has been placed in your Experiment Directory:
----------------------------------------------------------------------
----------------------------------------------------------------------
/discover/nobackup/aeichman/Ganymed-4_1/Linux/bin/GEOSgcm.x
/discover/nobackup/aeichman/Heracles-4_0/Linux/bin/GEOSgcm.x