Creating GEOS-Chem run directories

From Geos-chem
Revision as of 20:53, 19 March 2015 by Bmy (Talk | contribs) (Generating a copy of a run directory)

Jump to: navigation, search

On this page we show you how to use the GEOS-Chem Unit Tester to generate fresh copies of run directories for your GEOS-Chem simulations.

Downloading the GEOS-Chem unit tester

First, make sure that your system has these software packages installed. (Most of these come standard with your Unix-based operating system.)

Next, clone the GEOS-Chem unit tester package with the command:

git clone -b v10-01-public git:// UT

This will create a copy of the GEOS-Chem Unit Tester package in a directory named UT for short.

The option

-b v10-01-public

specifies which branch of the GEOS-Chem Unit Tester that you would like to download. Branches in the GEOS-Chem unit tester correspond to each internal version of GEOS-Chem (i.e. the states of the code for which we run 1-month benchmark simulations), as well as the publicly-released versions. Most likely, you will want to download the v10-01-public branch of the GEOS-Chem Unit Tester, which corresponds to the public release of GEOS-Chem v10-01.

--Bob Y. 13:36, 19 March 2015 (EDT)

Editing the CopyRunDirs.input file

Once you have downloaded the GEOS-Chem Unit Tester to your disk space, switch to the perl/ directory:

cd UT/perl

In this directory there is a Perl script named gcCopyRunDirs that you will use to generate fresh copies of GEOS-Chem run directories. This script uses an input file named CopyRunDirs.input, which is also located in the perl directory.

Your CopyRunDirs.input file will look something like this:

#                  GEOS-Chem Global Chemical Transport Model                  !
# !DESCRIPTION: Input file that specifies configuration for creating and
#  copying a run directory from the UnitTester. 
#  Customize the run directory for your system by specifying these values:
#  -------------------------------------------------------------------
#  VERSION     : A tag used to identify this Unit Test (e.g. v10-01h)
#  DESCRIPTION : A short description of this file's run dir copy configuration
#  COPY_PATH   : Local path where run directory will be copied to
#  DATA_ROOT   : Root GEOS-Chem data directory
#  HEMCO_ROOT  : Root directory where HEMCO emissions data files are stored 
#  RUN_ROOT    : Unit test run directories are subdirectories of RUN_ROOT
#  RUN_DIR     : Individual unit test run directory path
#  PERL_DIR    : Unit Test perl script directory (i.e. this directory)
#  COPY_CMD    : Unix copy command with optional tags
#  18 Mar 2015 - R. Yantosca - Initial version
#  19 Mar 2015 - E. Lundgren - Simplify content for only copying run dirs
   VERSION     : v10-01h
   DESCRIPTION : Create run directory from UnitTest
   COPY_PATH   : /home/{USER}/GC/rundirs
   DATA_ROOT   : /as/data/geos/ExtData
   RUN_ROOT    : /home/{USER}/UT/runs
   PERL_DIR    : /home/{USER}/UT/perl
   COPY_CMD    : cp -rfL
# !RUNS:
#  Specify the debugging runs that you want to perform below.
#  You can deactivate runs by commenting them out with "#".
  geosfp   2x25        -      Hg           2013070100   2013070101   -
  geos5    2x25        -      Hg           2005070100   2005070101   -
  geosfp   4x5         -      fullchem     2013070100   2013070101   -
  geos4    4x5         -      Hg           2005070100   2005070101   -
  geos4    4x5         -      CH4          2005070100   2005070101   -
  geosfp   4x5         -      Hg           2013070100   2013070101   -
  geosfp   4x5         -      POPs         2013070100   2013070101   -

NOTE: Lines starting with a # character will be treated as comments.

The CopyRunDirs.input file has a layout that is very similar to the GEOS-Chem Unit Tester input files. (These are the files named UnitTest.input, etc.) Like the GEOS-Chem Unit Tester input files, CopyRunDirs.input is composed of an !INPUTS section and a !RUNS section, which are described below.

Section 1: INPUTS

Under the !INPUTS: section, you can customize the directory paths and other options for your system. As seen above, most of these inputs are self-explanatory.

Option Description
VERSION An ID tag that will be added to all log files and output files.
DESCRIPTION A short (1-sentence) description of the purpose of this specific file (optional). This may be used to differentiate different input files, such as if you pre-configure several for future re-use.
COPY_PATH Specifies the root directory on your disk server where copies of the GEOS-Chem run directories will be created.
DATA_ROOT Specifies the path for your root-level data directory.
HEMCO_ROOT Specifies the top-level path for the HEMCO data directory tree.
  • The {DATAROOT} token in HEMCO_ROOT will be replaced with the value you specify for RUN_ROOT option.

Leave this as-is.

RUN_ROOT Specifies the top-level unit test run directories.

Leave this as-is.

PERL_DIR Specifies the directory where the unit test Perl scripts are found.

Leave this as-is.

COPY_CMD Specifies the command used to copy run directories from the GEOS-Chem Unit Tester to COPY_PATH.
  • The default setting is cp -rfL. This will create a new copy of the directory, even if the prior copy exists.
  • The -L option to the cp will create "hard" copies of files that are symbolic links. This command may differ slightly depending on the flavor of your Unix-based Operating system.

--Bob Y. 14:20, 19 March 2015 (EDT)

Section 2: RUNS

The layout of the !RUNS section is identical to The !RUNS section in the GEOS-Chem Unit Tester input files. This allows you to copy and paste text from one or more GEOS-Chem Unit Tester input files into CopyRunDirs.input.

For example, the following line:

# !RUNS:
#  Specify the debugging runs that you want to perform below.
#  You can deactivate runs by commenting them out with "#".
  geosfp   2x25        -      Hg           2013070100   2013070101   -

will tell the gcCopyRunDirs script to create a run directory for a GEOS-Chem simulation using:

The date range will be used to initialize the input.geos file that is read during a GEOS-Chem simulation. Once the run directory is created, you may edit these dates within the input.geos file. Note, however, that time ranges must remain within the time range covered by the MET field you are using. You can check the MET field temporal coverage on the GMAO met data products wiki page.

You can add as many entries to the !RUNS section as you wish. Simply cut and paste from one of the existing GEOS-Chem Unit Test input files (e.g. UnitTest.input within UT/perl).

Generating a copy of a run directory

Once you have edited the CopyRunDirs.input script to your liking, you can use that to generate fresh copies of GEOS-Chem run directories. Make sure you are in the perl directory, and then type:


If you do not pass a file name to gcCopyRunDirs, then the gcCopyRunDirs script will use the CopyRunDirs.input file that you just created.

If you wish, you can create many customized copies of CopyRunDirs.input. For example, suppose you edit CopyRunDirs.input to generate a mercury run directory. You can then save it as a separate file and use it explicitly with gcCopyRunDirs.

cp CopyRunDirs.input CopyRunDirs.Hg   # Input file set up to only copy the Hg run directories
gcCopyRunDirs CopyRunDirs.Hg                 

Executing gcCopyRunDirs will create a new GEOS-Chem run directory corresponding to each entry that you specified in the CopyRunDirs.* file. Each run directory will be created as a subdirectory of !COPY_PATH.

Let's examine the contents of a sample geosfp_2x25_Hg run directory. Issue the following commands:

cd ~/GC/rundirs/geosfp_2x25_Hg  # Change to geosfp_2x25_Hg run dir 
make fileclean                  # Remove any files left over from previous unit test runs

ls -l                           # Get detailed directory listing

And you will see this directory listing:

-rw-r--r-- 1 bmy bmy   17137 2015-03-18 16:18 HEMCO_Config.rc
-rw-r--r-- 1 bmy bmy   17116 2015-03-18 16:18 HEMCO_Config.template
-rw-r--r-- 1 bmy bmy    4568 2015-03-18 16:18 Makefile
-rwxr-xr-x 1 bmy bmy    1458 2015-03-18 16:18*
-rwxr-xr-x 1 bmy bmy    1374 2015-03-18 16:18*
-rw-r--r-- 1 bmy bmy 7391476 2015-03-18 16:18 initial_trac_rst.geosfp_2x25_Hg
-rw-r--r-- 1 bmy bmy   12082 2015-03-18 16:20 input.geos
-rw-r--r-- 1 bmy bmy   12060 2015-03-18 16:18 input.geos.template
-rw-r--r-- 1 bmy bmy  210712 2015-03-18 16:18 ocean_rst.geosfp_2x25_Hg.201307010000

NOTE: Run directories for other simulations may contain other files not pictured here.

The input.geos and HEMCO_Config.rc files have been customized for this particular simulation. They were created from the corresponding template files input.geos.template and HEMCO_Config.template. The template files are otherwise not used.

The Perl scripts and pass the starting and ending dates of the simulation, as specified in the input.geos file, to the Makefile.

--Bob Y. 14:24, 19 March 2015 (EDT)

Compiling and running GEOS-Chem

Once you have created one or more GEOS-Chem run directories, you can use them for your GEOS-Chem simulations. First, doublecheck that the settings in the input.geos and HEMCO_Config.rc files are correct for the simulation that you are trying to run. (We invite you to consult the GEOS-Chem Manual for more information about setting simulation options.)

To start a GEOS-Chem simulation, type the following commands. (We'll use the example of the geos5_2x25_Hg simulation, from the previous sections.)

make -j4 CODE_DIR=~/GC/Code.v10-01 VERSION=v10-01 MET=geosfp GRID=2x25 TRACEBACK=y mp

This will create the following output files:

File Description This is the HEMCO log file. Detailed information about the emissions that are being read from disk into HEMCO will be sent here. You can look at this file in order to determine there was an error in HEMCO caused by invalid input in the HEMCO_Config.rc file. This is the HEMCO restart file. Several quantities that are tracked by HEMCO are saved here, so that they can be used to initialize another GEOS-Chem simulation. This is the log file from the GEOS-Chem simulation. This is the diagnostic output file (aka the "binary punch file") that contains time-averaged output. This is the GEOS-Chem tracer restart file. Tracer concentrations are saved here so that they can be used to initialize another GEOS-Chem simulation. This is the ocean mercury restart file. This file is only produced by the GEOS-Chem mercury specialty simulation. Several quantities pertaining to the ocean mercury module are saved here so that they can be used to initialize another GEOS-Chem mercury simulation
diaginfo.dat Contains diagnostic quantities for GAMAP. This file is created by GEOS-Chem.
tracerinfo.dat Contains tracer name metadata for GAMAP. This file is created by GEOS-Chem.

NOTE: If you wish, you can omit the VERSION option. In this case, the version ID string will automatically be set to GC and the GEOS-Chem log file name will be, etc.

If you wish, you can also start a GEOS-Chem simulation without OpenMP parallelization by typing:

make -j4 CODE_DIR=~/GC/Code.v10-01 VERSION=v10-01 MET=geosfp GRID=2x25 TRACEBACK=y sp

In this case the output files in the table above will have the .sp suffix for single processor instead of .mp for multiprocessor.

--Bob Y. 15:58, 19 March 2015 (EDT)