Configuration¶
The configuration of MODIPSL-based models and experiments is distributed between many directories and files. The sheer amount of these elements requires from us a systematic documentation of all the existing intricacies. If you just want to run a default experiment, you can freely skip to the next part.
Experiment flavours¶
The definition of MODIPSL experiments is decoupled from the MODIPSL itself.
It is stored in a separate SVN repository at igcmg/CONFIG.
However, when we have selected a specific model in the installation section (e.g. ./model IPSLCM7_work),
the repository with experiments was cloned as well.
When inspecting the config/IPSLCM7/EXPERIMENTS/ directory, the result should be similar to this:
❯ tree config/IPSLCM7/EXPERIMENTS/ -d -L 2
config/IPSLCM7/EXPERIMENTS/
├── ICOLMDZ
│ ├── aquaplanet
│ ├── clim_noleap
│ ├── CREATE_amip
│ ├── CREATE_hadisst
│ └── LAM
├── ICOLMDZISO
│ ├── amip
│ ├── CREATE_amip
│ ├── CREATE_clim
│ └── piCtrl
├── ICOLMDZOR
│ ├── clim_pdControl.orch22
│ ├── clim_pdControl.orch4
│ └── LAM
...
First, you can see different types of experiments targeting various sets of components:
- ICOLMDZ - dynamics (DYNAMICO) and physics (LMDZ)
- ICOLMDZISO - dynamics (DYNAMICO), physics (LMDZ) with isotopes (ISOTOPES)
- ICOLMDZOR - dynamics (DYNAMICO) and physics (LMDZ) and land surface model (ORCHIDEE)
Second, only some of them have the LAM-specific experiments. In this and the next section, we will focus on the ICOLMDZ LAM experiments, because they are the simplest LAM configurations possible.
ICOLMDZ-LAM flavours¶
The classical LAM experiments are divided into two parts:
- Creation of initial state (
CREATE) - Running of the simulation (
TEST)
In the ICOLMDZ-LAM flavours, we can find the first step in the CREATE_amip* runs
and the second step in the amip* runs. The TEST name is often skipped from
the run name, but CREATE is usually there.
❯ tree config/IPSLCM7/EXPERIMENTS/ICOLMDZ/LAM -L 1
config/IPSLCM7/EXPERIMENTS/ICOLMDZ/LAM
├── amip
├── amip_ERA5_LAM
├── amip_ERA5_LAM_nbp20
├── amip_LAM
├── amip_LAM_nbp20
├── amip_nbp20
├── CREATE_amip
├── CREATE_amip_ERA5_LAM
├── CREATE_amip_ERA5_LAM_nbp20
├── CREATE_amip_LAM
├── CREATE_amip_LAM_nbp20
└── CREATE_amip_nbp20
The LAM simulations require input forcing data on the borders to pretend that it is part of a global simulation. This data can be either external, e.g. from the ERA5 dataset, or it can be generated using global AMIP simulation.
If you have the forcing data, you need to run CREATE_amip*_LAM followed by
corresponding amip*_LAM.
If not, run first CREATE_amip, followed by amip to create the forcing data.
Simulations with the lower resolution named with the nbp20 suffix are designed for
less powerful machines like ESPIR/Spirit(x).
Experiment configuration¶
Each experiment starts with a single entry-file called config.card containing, e.g.
experiment name, start and end dates, simulation period, list of components (like DYNAMICO, LMDZ, or XIOS),
among many others.
[Compatibility]
libIGCM=1.0
[UserChoices]
JobName=TEST-AMIP.01
LongName=""
TagName=ICOLMDZ
ExpType=ICOLMDZ/LAM/amip
ExperimentName=amip
SpaceName=DEVT
CreateName=CREATE-AMIP.01
#D-- leap, noleap, 360d
CalendarType=leap
DateBegin=2000-06-01
DateEnd=2000-06-05
#============================
#D-- 1Y, 1M, 5D, 1D
PeriodLength=5D
#============================
#-- Compression level for netcdf output files
CompressionLevel=2
#============================
# Source following file with module settings
EnvFile=${SUBMIT_DIR}/../ARCH/arch.env
#============================
# OptMode indicates the optimization mode choosen during compilation
# This variable is used in the executable name
OptMode=prod
[ListOfComponents]
ICO= (dynamico, DYNAMICO)
ATM= (lmdz, LMDZ)
IOS= (xios, XIOS)
[Executable]
ICO= (icosa_lmdz_orch22_${OptMode}.exe, icosa_lmdz.exe, 640MPI)
ATM= ("","")
IOS= (xios_server_${OptMode}.exe, xios.x, 1MPI)
[Restarts]
OverRule=n
RestartDate=
RestartJobName=
RestartPath=
[Post]
PackFrequency=NONE
TimeSeriesFrequency=NONE
SeasonalFrequency=NONE
MetricsPCMDI=FALSE
[ATM]
Restart= n
RestartDate=
RestartJobName=
RestartPath=
...
Component configuration¶
The majority of components use shared and its specific configuration. Other components, like IOIPSL, have no particular configuration and are used as-is.
Shared configuration¶
Mostly XIOS with *.xml files.
Per-component configuration¶
Mainly *.def files.