To make a model run, some directory paths must be defined:
These paths are set by the user in the job script, as in these examples: (these can be absolute paths or relative to the working directory):
set modeldir = tiegcm_trunk
set tgcmdata = /my/prettybig/data/tiegcm.data
set execdir = /my/big/exec/disk/tiegcm.exec
See this example job script
To get started, the user will typically create a working directory from which model runs are submitted. The user’s working directory will typically look something like this:
workdir
|
-----------------------------------------------
| |
*.inp modeldir/
*.job
*.out
Here, *.inp are namelist input files, *.job are job script‘s, and *.out are stdout output files from model and are validated by the input module (input.F).
The job script in your working directory contains a shell variable specifying the path to the modeldir, so it knows where to find the source code and supporting scripts for the build process. The namelist input file also refers to the datadir path for start-up and other data input files (e.g., SOURCE, GPI_NCFILE, IMF_NCFILE, etc). These namelist parameters can use the environment variable TGCMDATA to specify the datadir (see section on namelist input files). The job script shell variable tgcmdata, if set, will override the TGCMDATA env var.
The model root directory is what you get when you download the model source code tar file, or check out the code from the svn repository. The model directory contains subdirectories with the model source code, supporting scripts, documentation, and a python code to make test and benchmark runs:
modeldir
|
-------------------------------------------------------------------------
| | | | |
src/ scripts/ doc/ tgcmrun/ benchmarks/
| | | | |
*.F90 Make.* userguide/ *.py run_climatology
*.F linux.job description/ run_* run_seasons
*.h ibm.job release/ tgcmrun run_storms
default.inp diags.table archive_hpss
tgcm_contents perf.table make_listings
tgcm_ncdump README.download postproc/
etc
src/ directory contents:
scripts/ directory contents:
There are several additional utilities in the scripts directory that are used by the build system or by the user to perform various tasks or to obtain information (see README in scripts directory for more information). directory for more information.
doc/ directory contents:
tgcmrun/ directory contents:
benchmarks/ directory contents:
The public TIEGCM data directory is what you get when you download the data tar file. This directory is typically referred to with the environment variable TGCMDATA, but can be set with the tgcmdata shell variable in the job script (the shell variable, if set, will take precedence over the environment variable):
datadir for tiegcmx.x
|
----------------------------------------------
|
tiegcmx.x_res5.0_*.nc
tiegcmx.x_res2.5_*.nc
gpi*.nc
gswm*5.0d*.nc
gswm*2.5d*.nc
imf_OMNI_*.nc
etc
These are netCDF history startup and data files for running the current version of the model ( tiegcm2.0 ) They are specified in the namelist input file (see namelist input files for more information). These files are available for download, see Downloading the model source code and required data files.
tiegcmx.x_res5.0_*.nc: History start-up files for the 5.0-degree resolution model. These files contain a single history with initial conditions for starting the model at a specific date and time. These are typically the first history for a benchmark run (seasonal, storm simulations, and climatologies). Namelist input parameter: SOURCE. Here are the files for tiegcm2.0:
tiegcmx.x_res2.5_*.nc: History start-up files for the 2.5-degree resolution model. These files contain a single history with initial conditions for starting the model at a specific model date and time. These are typically the first history for a benchmark run (seasonal, storm simulations, and climatologies). Namelist input parameter: SOURCE Here are the files for tiegcm2.0:
gpi*.nc GeoPhysical Indices data files (3-hourly Kp and F10.7 cm solar flux). Namelist Input parameter: GPI_NCFILE
gswm*5.0d*.nc Global Scale Wave Model data files, used to specify tidal perturbations for the lower boundary of the TIEGCM for the 5-degree resolution. There are 4 separate files for diurnal, semi-diurnal, migrating and non-migrating tides. Namelist Input parameter: GSWM.
gswm*2.5d*.nc Global Scale Wave Model data files, used to specify tidal perturbations for the lower boundary of the TIEGCM for the 2.5-degree resolution. There are 4 separate files for diurnal, semi-diurnal, migrating and non-migrating tides. Namelist Input parameter: GSWM.
imf_OMNI_*.nc Interplanetary Magnetic Field OMNI data files. Namelist read parameter is IMF_NCFILE. These files contain data for the BX,BY,BZ components of the IMF, solar wind velocity and solar wind density. See HAO public ftp page to download imf data files for years not included on the tiegcm2.0 data download.
The model is built and executed in the execution directory (execdir). The path to the execution directory is specified by the execdir shell variable in the job script. The job script will create the execdir for you if it does not already exist. The following file types are typically found in the execution directory:
Note
When making your first run, its best to let the job script create the execdir for you. It is not wise to use an execdir used for revisions prior to tiegcm2.0. Also, if you have build or execution problems, it will sometimes help to remove the execdir and let the job script start over.
The model executable also resides in the execution directory.