Version 1 (modified by jgipsl, 2 years ago) (diff)


The LMDZOR_v6.2 configuration

LMDZOR_v6.2 is a configuration close the the coupled configuration IPSLCM6.2

Person in charge: Josefine Ghattas

1. Description

LMDZOR_v6.2 configuration contains the atmospheric model LMDZ and the land surface model ORCHIDEE. This configuration is under construction and the versions of the models might change without any announcement. If you want to use this version, contact the reference person above.

1.1. Main differences between LMDZOR_v6.2 and LMDZOR_v6.1.10

LMDZOR_v6.2 :

  • is adapted to the trunk version of LMDZ and version ORCHIDEE_2_2. These versions are slightly different from the versions used for CMIP6.
  • a compilation script is used instead of a makefile in config/LMDZOR_v6 folder.
  • the configuration is independent of the default module environnement as during compilation a file in config/LMDZOR_v6/ARCH is used
  • no possibility to use the old 2-bucket hydrology scheme Choisnel in ORCHIDEE

1.2. Compiling

To be done

1.3. Launching

The default set up is using 71 MPI * 8 OMP for the gcm.e and 1 MPI for the xios server. Following is set in config.card :

ATM= (gcm_${ResolAtm}_${OptMode}.e, lmdz.x, 71MPI, 8OMP)
SRF= ("", "")
SBG= ("", "")
IOS= (xios_server_${OptMode}.exe, xios.x, 1MPI)

1.4. XIOS and output control

XIOS is 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.2 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.

The output level and the files to write is set in lmdz.card, orchidee.card and stomate.card. See comments in the corresponding files and read more in chapter Setup?. The WriteFrequency option in config.card is not used any more.

1.5. Parameter files

Parameter file are found in PARAM/ directory except the xml files copied directly from the models directory.

In the parameter files, some of the variables will be modified after the job is submitted. This is done by the comp.driver: lmdz.driver, orchidee.driver, stomate.driver and xios.driver. All the variables that might be modified are set equal _AUTO_ or _AUTOBLOCKER_. No variable can be modified without having this key word. The values for these variables 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.

Physics in LMDZ:
Different versions of physics for LMDZ exist in PARAM directory. The choice is done from lmdz.card by setting the variable LMDZ_Physics. The physiq.def and gcm.def files are suffixed by the version of the physics.

CWRR 11-layer hydrology in ORCHIDEE:
Only the multilayer CWRR hydrology scheme is available in ORCHIDEE.

2. Quick installation

2.1. Extract default version

# Install modipsl
svn co modipsl
cd modipsl/util

# Before next command, modify the file mod.def if you want to extract an old version (*)

# Download and compile configuration LMDZOR_v6.2_work
./model LMDZOR_v6.2_work
cd ../config/LMDZOR_v6
./ [-debug, ...]

# Experiment setup
cp EXPERIMENT/LMDZOR/clim_pdControl/config.card .     # => modify at least JobName=MyJobname, DateBegin, DateEnd in config.card
cd MyJobname

# Modify default setup: 
# for example change physics in lmdz.card, or hydrology in orchidee.card

# Modify config.card if compilation done for debug mode or another resolution than the default 144x142x79
vi config.card  => OptMode=debug, ResolAtm=xxx

ccc_msub Job_MyJobname / sbatch Job_MyJobname

2.2. Extract a different version

Modify the file util/mod.def if you do not want the default set up. This must be done at step (*) above, before the command ./model LMDZOR_v6.2_work. Look for the lines starting with #-C- LMDZOR_v6.2_work. Each of these lines describes the extraction of one component which is included in the configuration LMDZOR_v6.2. Change the revision number to correspond to the revision you need.

3. How to reproduce a coupled simulation with the forced model ?

To be reviewed...

You have run a simulation with IPSLCM6 and you would like to launch the same with LMDZOR_v6.2 with limit conditions (SST and seaice) coming from the same or another IPSLCM6 simulation. In practice this is needed to estimate radiative forcing from MyIPSLCM6 experiment using SST and sea-ice from the same simulation or from a reference simulation

For this you need to follow all these steps :

  • Create using sst / sic and land-sea mask from your IPSLCM6 simulation, as described here
  • Create your new experiment directory
    cd modipsl/config/IPSLCM6
    cp -r MyIPSLCM6 MyLmdzor6
    cd MyLmdzor6
    rm -rf Script* run.card Job* Debug
  • modify config.card :
    • modify the JobName as you want
    • modify the TagName to LMDZOR
    • modify the Restart section to use Restart from MyIPSLCM6
    • remove or comment out all lines for the ocean component(OCE, MBG) and the coupler(CPL) in ListOfCompondents and Executable section :
      #D-- ListOfComponents -
      #D- For each component, Name of component, Tag of component
      ATM= (lmdz, LMDZ4-dev)
      SRF= (orchidee, ORCHIDEE_1_9_5)
      SBG= (stomate, ORCHIDEE_1_9_5)
      #OCE= (opa9, CMIP5_IPSL)
      #ICE= (lim2, CMIP5_IPSL)
      #MBG= (pisces, CMIP5_IPSL)
      #CPL= (oasis, OASIS3-MCT)
      IOS= (xios, XIOS)
      #D-- Executable -
      #D- For each component, Real name of executable, Name of executable for oasis
      ATM= (gcm.e, lmdz.x, 32MPI, 4OMP)
      SRF= ("" ,"" )
      SBG= ("" ,"" )
      #OCE= (opa, opa.xx, 31MPI)
      #ICE= ("" ,"" )
      #MBG= ("" ,"" )
      #CPL= ("", "" )
      IOS= (xios_server.exe, xios.x, 1MPI)
  • Add the path of your new files in [BoundaryFiles] Section of lmdz.card
  • (If you are working with IPSLCM5A you need to put "type_ocean=force" in PARAM/run.def)
  • create your new job