Note: Order of precedence for how variables are evaluated - 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 used with provided when calling oifs-run, then the default settings found inside oifs-run are used instead (Not 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 it 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 the 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.
Best practice: You should always set up an exp-config.h for each experiment. If no exp-config.h file is found in the experiment directory, and if also no command line parameters are provided when calling oifs-run, then oifs-run will revert to its own default values which are not appropriate. In any case you should either edit the exp-config.h file appropriately or provide the correct command line parameters. |