GEM/4.6/Running the model

From Wiki
< GEM | 4.6
Jump to: navigation, search

Running the GEM model simply consists of setting a few configuration files then running a few scripts that will eventually take care of the three major components of the model execution:

1) Entry: will run the binary maingemntr (model pre-processing)
2) Model: will run the binary maingemdm (main time loop)
3) Output: will run post-processing of model output

Contents

[hide]

1 Configuration

The execution of all 3 components is highly configurable through the use of 3 configuration files called:

gem_settings.nml File containing some namelists to configure the model execution
outcfg.out File use to configure the model output
configexp.cfg File use to configure the execution shell environment

The specific content of those 3 files is documented on the wiki. Exemples of configuration files can be found at $gemdyn/include/configs
In particular the content of $gemdyn/include/configs/bcmk can be used by beginners to run a small development case.

NOTE: The default configs mentioned above are NOT currently available for Gem 4.6.0

Other examples can be found in the test cases.

2 Running

Put the configurations files (gem_settings.nml outcfg.out configexp.cfg) in a directory structure as follow :

exp_dir/cfg_0000

The master directory name (exp_dir in the example above) can be any valid directory name. However, the second directory must have the name cfg_XXXX where XXXX represent numbers from 0000 to 9999. If one just runs one experiment, it is practical to call it cfg_0000 since this is the default value.

After the model environment has been established ( . s.ssmuse.dot GEM/4.6.0) the model is ready to launch using either an interactive or batch method.

2.1 Running interactively

To run the entree

Um_runent.ksh -dircfg exp_dir

To run the model

Um_runmod.ksh -dircfg exp_dir

2.2 Running in batch mode

Um_lance exp_dir/cfg_0000
Note: the model output will always end up at the location specified by the user in the file configexp.cfg with the variable
GEM_xfer=my_machine:my_directory