Skip navigation
NASA Logo, National Aeronautics and Space Administration
Modeling Guru Banner
Currently Being Moderated

Fortuna 2-5 User's Guide

VERSION 2  Click to view document history
Created on: Nov 8, 2011 8:02 AM by Carlos Cruz - Last Modified:  Nov 28, 2012 10:10 AM by Carlos Cruz

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 ).


Setting up a Global Model Run

The following describes how to set up a global model run.

Using  gcm_setup

The setup script for global runs,  gcm_setup , is in the directory  src/Applications/GEOSgcm_App . The following is an example of a session with the setup script, with commentary.  :


 Enter the Experiment ID:


Enter a name and hit return. For this example we'll set the experiment ID to "myexp42". Experiment IDs need to have no whitespace and not start with a digit, since it will be the prefix of job names and PBS imposes certain limits on job names.


Enter a 1-line Experiment Description:


This should be short but descriptive, since it will be used to label plots. It can have spaces, though the string will be stored with underscores for the spaces. Provide a description and hit return.


Enter the Lat/Lon Horizontal Resolution: IM JM
   or ..... the Cubed-Sphere Resolution: cNN


The lat/lon option allows four resolutions: 144x91, 288x181, 576x361 or 1152x721 corresponding rougly to 2, 1, 1/2 and 1/4 degree resolutions. Enter a resolution like so:


144 91


and hit enter.


Enter the Model Vertical Resolution: LM (Default: 72)


The current standard is 72 levels, and unless you know what you are doing you should stick with that.


Do you wish to run GOCART? (Default: NO or FALSE)


GOCART is the interactive chemistry package, as opposed to prescribed chemistry. It incurs a significant performance cost, so unless you know you want it, you should go with the default. The following assumes that you have entered "y".


Enter the GOCART Emission Files to use: "CMIP" (Default), "PIESA", or "OPS":


Select your favorite emission files here.


Enter the AERO_PROVIDER: GOCART (Default) or PCHEM:


Here you get to choose again to use interactive or prescribed aerosols.


Enter the tag or directory (/filename) of the HISTORY.AGCM.rc.tmpl to use
(To use HISTORY.AGCM.rc.tmpl from current build, Type:  Current         )
Hit ENTER to use Default Tag/Location: (Fortuna-2_5)


This provides a default HISTORY.rc (output specification) file. The initial default will be the tag of the build in which you are running  gcm_setup . The idea is that you can save a custom  HISTORY.rc  to the repository and have it checked out for your experiments.


Enter Desired Location for HOME Directory (to contain scripts and RC files)
Hit ENTER to use Default Location:
Default:  /discover/nobackup/aeichman/myexp42


This option determines where the experiment's home directory is located -- where the basic job scripts and major RC files ( AGCM.rc ,  CAP.rc  and  HISTORY.rc ) will be located. The first time you run the script it will default to a subdirectory under your account's home directory named  geos5 , remember what you decide (in  ~/.HOMDIRroot ) and use that as a default in subsequent times the script is run. This initial default is fine, though another possibility is to enter your nobackup space, as shown here. This will place all of the HOME directory files of the experiment together with the rest of them.


Enter Desired Location for EXP Directory (to contain model output and restart files)
Hit ENTER to use Default Location:
Default:  /discover/nobackup/aeichman/myexp42


This determines the experiment directory, where restart files and various job output is stored. These are the storage-intensive parts and so default to the  nobackup  space.


Enter Location for Build directory containing:  src/ Linux/ etc...
Hit ENTER to use Default Location:
Default:  /discover/nobackup/aeichman/Fortuna-2_5


This determines which of your local builds is used to create the experiment. It defaults to the build of the script you are running, which is generally a good idea.


Current GROUPS: g0620
Enter your GROUP ID for Current EXP: (Default: g0620)


This is used for by the job accounting system. If you are not in the default group, you will probably have been informed.



building file list ... done

sent 50117242 bytes  received 42 bytes  33411522.67 bytes/sec
total size is 50110997  speedup is 1.00
Creating gcm_run.j for Experiment myexp42 ...
Creating gcm_post.j for Experiment myexp42 ...
Creating gcm_plot.j for Experiment myexp42 ...
Creating gcm_archive.j for Experiment myexp42 ...
Creating gcm_regress.j for Experiment myexp42 ...
Creating AGCM.rc for Experiment myexp42 ...
Creating CAP.rc for Experiment myexp42 ...
Creating HISTORY.rc for Experiment myexp42 ...
Build Directory: /discover/nobackup/aeichman/Fortuna-2_5
The following executable has been placed in your Experiment Directory:
You must now copy your AGCM Initial Conditions into: 


And the experiment is set up. After you copy initial condition files (aka restarts) to the experiment directory, you can submit your job.


Do not copy old experiments

When creating related experiments, you will be tempted to copy the experiment directory tree of an older experiment. Do not copy old experiments, run  gcm_setup  instead. There are numerous instances where an experiment-specific directory is used in the run scripts created from templates by  gcm_setup  and they will wreak subtle and pervasive havoc if executed in an unexpected environment. This warning is especially true between model versions. A useful and relatively safe exception to this rule is to copy previously used examples of  HISTORY.rc . However, you need to change the lines labeled  EXPID  and  EXPDSC  to the values in your automatically-generated  HISTORY.rc  or the plotting will fail.


Using restart files

Restart files provide the initial conditions for a run, and a set needs to be copied into a fresh experiment directory before running. This includes the file  cap_restart , which provides the model starting date and time in text. Restart files themselves are resolution-specific and sometimes change between model versions. As of the current model version, they are flat binary files with no metadata, so they tend to be stored together with restarts of the same provinance with the date either embedded in the filename or in an accompanying  cap_restart , typically under a directory indicating the model version.

A cleanly completed model run will leave a set of restarts and the corresponding  cap_restart  in its experiment directory. Another source is  /archive/u/aeichman/restarts . Restarts are also left during runs in date-labeled tarballs in the  restarts  directory under the experiment directory before being transferred to the user's  /archive  space. You may have to create the  cap_restart , which is simply one line of text with the date of the restart files in the format YYYYMMDD HHMMSS (with a space).

Up to: Building and Installing the GEOS-5 AGCM

Return to: GEOS-5 AGCM User's Guide

Comments (0)
USAGov logo NASA Logo -