...
| Code Block |
|---|
| language | bash |
|---|
| title | exp-config.h |
|---|
|
#--- required variables for this experiment:
OIFS_EXPID="ab2aab7x" # your experiment ID
OIFS_NPROCRES=8"95" # the numberspectral ofgrid MPI tasksresolution
OIFS_NTHREAD=4 # the number of OpenMP threads
OIFS_GRIDTYPE="l" # the grid type, either 'l' for linear reduced grid, or 'o' for the cubic octahedral grid
OIFS_RESNPROC="255"8 # the number of # the spectral grid resolutionMPI tasks
OIFS_NAMELISTNTHREAD='fort.4'4 # the namenumber of the atmospheric namelist file (the default is fort.4, so this line could be omitted)
OIFS_EXE="${OIFS_HOME}/build/bin/ifsMASTER.DP" # the name and location of the model binary executable
OIFS_PPROC=true # enable postprocessing of model OpenMP threads
OIFS_PPROC=true # enable postprocessing of model output after the model run
OUTPUT_ROOT=$(pwd) # folder where pproc output is created (only used if OIFS_PPROC=true). In this case an output folder is created in the experiment directory.
LFORCE=falsetrue # overwrite existing symbolic links in the experiment directory
LAUNCH="" # the platform specific run command for the MPI environment (e.g. "mpirun", "srun", etc).
#--- optional variables that can be set for this experiment:
#OIFS_NAMELIST='my-fort.4' # custom atmospheric model namelist file
#OIFS_EXEC="<cutome-path>/ifsMASTER.DP" # model exec to be used for this experiment
|
| Info |
|---|
| title | Order of precedence for how OpenIFS evaluates variables: |
|---|
|
- exp-config.h: These variables have top precedence and are used for the experiment (Best practice to use this).
Example: Here you are setting the experiment ID, parameters for the model grid and for parallel execution of this specific experiment. Each experiment directory should contain its own exp-config.h file.
- oifs-run: If no exp-config.h is found, and if no command-line parameters are provided when calling oifs-run, then the default settings found inside oifs-run are used instead (This is not recommended! Use an exp-config.h file instead).
Example: For some variables the defaults are usually fine. For instance, you do not need to specify the namelist file 'fort.4' in exp-config.h, because oifs-run will use this file name as a default value.
- oifs-config.edit_me.sh: This file contains global configuration settings required for the correct functioning of OpenIFS, and therefore this file needs to be always sourced first. However, it does not contain variables that are specific to a forecast experiment, and any variables that are declared in either exp-config.h or in oifs-run will overwrite their previous settings in this global configuration file.
Example: In your global configuration file you may have set the double precision variable as your standard model executable. If you wish to use single precision for a specific experiment, then you can set OIFS_EXEC in exp-config.h to the SP binary executable which will overwrite the global setting for this experiment.
|
Running the experiment
After all optional edits to the namelists (fort.4) and to the experiment configuration file (exp-config.h) have been completed the model run can be started.
...