Ganymed 4.0 User's Guide: Difference between revisions
m →Compiling the Model: Use Ganymed not Fortuna as module name |
|||
| (3 intermediate revisions by one other user not shown) | |||
| Line 7: | Line 7: | ||
Most of the time for longer runs you will be using a release version of the model, perhaps compiled with a different version of one or more of the model's gridded components, as defined by subdirectories in the source code. This process starts with checking out the stock model from the repository using the command | Most of the time for longer runs you will be using a release version of the model, perhaps compiled with a different version of one or more of the model's gridded components, as defined by subdirectories in the source code. This process starts with checking out the stock model from the repository using the command | ||
cvs co -r ''TAGNAME'' -d ''DIRECTORY'' | cvs co -r ''TAGNAME'' -d ''DIRECTORY'' Ganymed | ||
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_0_BETA8</code>, indicating the latest patch of version Ganymed 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>Ganymed-4_0_BETA8</code>, indicating the latest patch of version Ganymed 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. | ||
| Line 130: | Line 130: | ||
Hit ENTER to use Default Location: | Hit ENTER to use Default Location: | ||
---------------------------------- | ---------------------------------- | ||
Default: /discover/nobackup/aeichman/Ganymed- | Default: /discover/nobackup/aeichman/Ganymed-4_0_BETA8 | ||
</pre> | </pre> | ||
| Line 136: | Line 136: | ||
<pre> | <pre> | ||
Current GROUPS: g0620 | Current GROUPS: g0620 gmaoint q_warp q_warp-test | ||
Enter your GROUP ID for Current EXP: (Default: g0620) | Enter your GROUP ID for Current EXP: (Default: g0620) | ||
</pre> | </pre> | ||
| Line 166: | Line 166: | ||
Done! | Done! | ||
----- | ----- | ||
Build Directory: /discover/nobackup/aeichman/Ganymed- | Build Directory: /discover/nobackup/aeichman/ Ganymed-4_0_BETA8 | ||
---------------- | ---------------- | ||
| 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- | /discover/nobackup/aeichman/Ganymed-4_0_BETA8/Linux/bin/GEOSgcm.x | ||
| Line 196: | Line 196: | ||
A cleanly completed model run will leave a set of restarts and the corresponding <code>cap_restart</code> in its experiment directory. Another source is <code>/archive/u/aeichman/restarts</code>. Restarts are also left during runs in date-labeled tarballs in the <code>restarts</code> directory under the experiment directory before being transferred to the user's <code>/archive</code> space. You may have to create the <code>cap_restart</code>, which is simply one line of text with the date of the restart files in the format ''YYYYMMDD HHMMSS'' (with a space). | A cleanly completed model run will leave a set of restarts and the corresponding <code>cap_restart</code> in its experiment directory. Another source is <code>/archive/u/aeichman/restarts</code>. Restarts are also left during runs in date-labeled tarballs in the <code>restarts</code> directory under the experiment directory before being transferred to the user's <code>/archive</code> space. You may have to create the <code>cap_restart</code>, which is simply one line of text with the date of the restart files in the format ''YYYYMMDD HHMMSS'' (with a space). | ||
Failing the above sources, you can convert restarts from different resolutions and model versions, including MERRA, as described in [[Regridding Restarts for Ganymed | Failing the above sources, you can convert restarts from different resolutions and model versions, including MERRA, as described in [[Regridding Restarts for Ganymed 4.0]]. | ||
== What Happens During a Run == | == What Happens During a Run == | ||