Ganymed 4.0 User's Guide: Difference between revisions

Line 1:

This page describes in detail how to set up and optimize a global model run of GEOS-5 Ganymed 3.0 on NCCS discover and NAS pleiades and generally make the model do what you want. It assumes that you have already run the model as described in [[Ganymed 3.0 Quick Start]].

This page describes in detail how to set up and optimize a global model run of GEOS-5 Ganymed 4.0 on NCCS discover and NAS pleiades and generally make the model do what you want. It assumes that you have already run the model as described in [[Ganymed 4.0 Quick Start]].

'''Back to [[GEOS-5 Documentation for Ganymed 3.0]]'''

'''Back to [[GEOS-5 Documentation for Ganymed 4.0]]'''

== Compiling the Model ==

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, 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'' Fortuna

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-~~3_0_p1~~</code>, indicating the latest patch of version Ganymed 3.0 for general use ~~(there is a <code>Ganymed-3_0_p2</code> patch for operations -- don't use it unless you know otherwise)~~. ''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.

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 1: / Line 1: @@
-This page describes in detail how to set up and optimize a global model run of GEOS-5 Ganymed 3.0 on NCCS discover and NAS pleiades and generally make the model do what you want.  It assumes that you have already run the model as described in [[Ganymed 3.0 Quick Start]].
+This page describes in detail how to set up and optimize a global model run of GEOS-5 Ganymed 4.0 on NCCS discover and NAS pleiades and generally make the model do what you want.  It assumes that you have already run the model as described in [[Ganymed 4.0 Quick Start]].
-'''Back to [[GEOS-5 Documentation for Ganymed 3.0]]'''
+'''Back to [[GEOS-5 Documentation for Ganymed 4.0]]'''
 == Compiling the Model ==
-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, 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'' Fortuna
-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-3_0_p1</code>, indicating the latest patch of version Ganymed 3.0 for general use (there is a <code>Ganymed-3_0_p2</code> patch for operations -- don't use it unless you know otherwise). ''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.
 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