Fortuna 2.4 User's Guide: Difference between revisions

Line 11:

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>Fortuna-2_4_p2</code>, indicating the version Fortuna 2.4 patch 2. ''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> to the <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

cvs upd -r ''VARIANT_TAGNAME''

The source code will then ~~contain~~ the tag's modifications.

The source code will then incorporate the tag's modifications.

Once the checkout from the repository is completed, you are ready to compile. <code>cd</code> to the <code>src</code> directory at the top of the source code directory tree and from a <code>csh</code> shell run <code>source g5_modules</code>. This will load the appropriate modules and create the necessary environment for compiling and running. It is tailored to the individual systems that GEOS-5 usually runs on, so it probably won't work elsewhere. After that you can run <code>make install</code>, which will create the executables.

Once the checkout from the repository is completed, you are ready to compile. <code>cd</code> to the <code>src</code> directory at the top of the source code directory tree and from a <code>csh</code> shell run <code>source g5_modules</code>. This will load the appropriate modules and create the necessary environment for compiling and running. It is tailored to the individual systems that GEOS-5 usually runs on, so it probably won't work elsewhere. After that you can run <code>make install</code>, which will create the necessary executables in the directory ''ARCH''/bin, where ''ARCH'' is the local architecture (most often <code>Linux</code>).

== Setting up a Global Model Run ==

@@ Line 11: / Line 11: @@
 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>Fortuna-2_4_p2</code>, indicating the version Fortuna 2.4 patch 2. ''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> to the <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
    cvs upd -r  ''VARIANT_TAGNAME''
-The source code will then contain the tag's modifications.
+The source code will then incorporate the tag's modifications.
-Once the checkout from the repository is completed, you are ready to compile.  <code>cd</code> to the <code>src</code> directory at the top of the source code directory tree and from a <code>csh</code> shell run <code>source g5_modules</code>.  This will load the appropriate modules and create the necessary environment for compiling and running.  It is tailored to the individual systems that GEOS-5 usually runs on, so it probably won't work elsewhere.  After that you can run <code>make install</code>, which will create the executables.
+Once the checkout from the repository is completed, you are ready to compile.  <code>cd</code> to the <code>src</code> directory at the top of the source code directory tree and from a <code>csh</code> shell run <code>source g5_modules</code>.  This will load the appropriate modules and create the necessary environment for compiling and running.  It is tailored to the individual systems that GEOS-5 usually runs on, so it probably won't work elsewhere.  After that you can run <code>make install</code>, which will create the necessary executables in the directory ''ARCH''/bin, where ''ARCH'' is the local architecture (most often <code>Linux</code>).
 == Setting up a Global Model Run ==