Fortuna 2.5 User's Guide
This page describes in detail how to set up and optimize a global model run of GEOS-5 Fortuna 2.5 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 Fortuna 2.5 Quick Start.
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
cvs co -r TAGNAME -d DIRECTORY Fortuna
where TAGNAME is the model "tag" (version). A tag in cvs 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 Fortuna-2_5, indicating the version Fortuna 2.5 (the latest version). 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 ESMADIR, 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 cd 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 cd several levels down to the directory GEOSsatsim_GridComp and run
cvs upd -r VARIANT_TAGNAME
The source code will then incorporate the tag's modifications.
Once the checkout from the repository is completed, you are ready to compile. cd to the src directory at the top of the source code directory tree and from a csh shell run source g5_modules. 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 make install, which will create the necessary executables in the directory ARCH/bin, where ARCH is the local architecture (most often Linux).