| Version 6 (modified by jgipsl, 9 years ago) (diff) |
|---|
The LMDZOR_v6 configuration
Table of contents
Table of contents
Person in charge: Josefine Ghattas
1. Description
LMDZOR_v6 is a configuration under construction. More information to come...
LMDZOR_v6 configuration contains the atmospheric model LMDZ and the land surface model ORCHIDEE. Currently this configuration contains the following components:
- LMDZ5 testing revision 2314
- ORCHIDEE trunk revision 2724
- XIOS branchs/xios-1.0 revision 604 (library for writing output files)
- IOIPSL (IOIPSL is not used for output anymore, only for restart files and other options)
- libIGCM trunk revision 1215
- configuration files for LMDZOR_v6 revision 2618
Default compilation is still 96x96x39. Default option during run time is old physics and 2-layer hydrology. These options can be changed.
1.1. Compiling
Default compilation is still 96x96x39 but other resolutions can be compiled. To compile 144x142x79 grid do as follow :
gmake LMD144142-L79
By default the compiling is done for hybrid MPI and OMP parallelism. It is not necessary to activate OMP threads during run time.
1.2. Launching
The default set up is using 31MPI for the gcm.e and 1MPI for the xios server. This is set in config.card :
#-- Total Number of Processors
JobNumProcTot=32
[Executable]
ATM= (gcm.e, lmdz.x, 31MPI, 1OMP)
SRF= ("", "")
SBG= ("", "")
IOS= (xios_server.exe, xios.x, 1MPI)
1.3. XIOS and controlling output
XIOS is the new component used for output writing. It consists of a library linked to the model and an external server executable (xios_server.exe). It can be launched in attached mode or in server mode. The default set up in LMDZOR_v6 is using the server mode with 1 MPI for the server. 2 executables are launched: gcm.e and xios_server.exe. No reconstruction is needed for the output files. The rebuild tool detects automatically that this is not needed.
LMDZOR_v6 is only using XIOS for writing diagnostic output files. The output is managed by xml files. The files beginning with file_def....xml are controlling the variables and the files that are written.
A basic level of output control is done from config.card with the variables WriteFrequency. For LMDZ it is also possible to change the level of output for the files using the variable OutLevel in lmdz.card. Finer control of the output must be done directly in PARAM/file_def_....xml files. Where it is set _AUTO_, it can be replaced manually for example in PARAM/file_def_histday_lmdz.xml :
<file id="histday" name="histday" output_freq="1d" output_level="_AUTO_" enabled="_AUTO_">
can be changed into
<file id="histday" name="histday" output_freq="1800s" output_level="1" enabled=".TRUE.">
1.4. Parameter files
Most parameter file are found in PARAM/ directory as for the v5 configurations. But some files are now also copied from the model directories. This is the case for field_def_lmdz.xml and field_def_orchidee.xml. In lmdz.card and orchidee.card you can see where the files are taken from.
In the parameter files, some of the variables will be modified after the job is submitted. All these variables are set equal _AUTO_ or _AUTOBLOCKER_. No variable can be modified without having this key word. This means that the real value will be set by the drivers when the job is submitted. The values are set according to the options from lmdz.card, orchidee.card, stomate.card and config.card.
A variable which is set to _AUTO_ can also be changed manually in the corresponding file in the PARAM directory. For this case, the driver can not change it again. Some variables are set equal _AUTOBLOCKER_. They cannot be changed. If still they are changed, the job will exit with error message.
2. Quick installation
# Installation and compilation svn co http://forge.ipsl.jussieu.fr/igcmg/svn/modipsl/trunk modipsl cd modipsl/util ./model LMDZOR_v6 cd ../condig/LMDZOR_v6 gmake [or gmake LMD144142-L79] # Experiment setup cp EXPERIMENT/LMDZOR/clim/config.card . # => modify at least JobName=MyJobname, DateBegin, DateEnd in config.card ../../util/ins_job cd MyJobname # Modify default setup: change physics in lmdz.card (for other physics than AP or NPv3.2 you also need to add physic.def_NPxxx in PARAM/) # change hydrology(2- or 11- layer) in orchidee.card ccc_msub Job_MyJobname / llsubmit Job_MyJobname
3. Simulations
- 10-year amip simulations done with LMDZ testing rev 2314 and ORCHIDEE rev 2724. The simulations are done with Choisnel (2 layer) versus CWRR (11 layer) hydrology in ORCHIDEE and both uses old physics(AP) in LMDZ.
- 10-year amip simulations done with LMDZ testing rev 2168 and ORCHIDEE rev 2724. The simulations are done with old physics (CL1 simulations) and NPv3.2 physics(CL2) in LMDZ and with both Choisnel (2 layer) versus CWRR (11 layer) hydrology in ORCHIDEE.
- Inter-monitoring with the simulations comparing LMDZ testing revision 2314 and 2168
