Version 26 (modified by nvuilsce, 8 years ago) (diff)


DocumentationMain VersionOther VersionsScriptsForcingsEvaluationToolsHow toMeetingsSeminarsUserListContact

Documentation for how to use ORCHIDEE with libIGCM and modipsl

ORCHIDEE is distributed using modipsl and scripts for libIGCM are available for running. To learn how to use these tools, read the platform/en/documentation and follow one of the platform courses. The documentations is now in english.

In complement to the platform documentation, you find in this wiki specific information and help to use ORCHIDEE.

libIGCM is an an Sytem Running Environment (SRE). It is used to manipulate input and output files for an executable (or a set of executables in a coupled configuration). libIGCM is a library of scripts to launch simulations and posttreatment. Modularity and portability make your jobs work on a several machines(super-computer center) used at IPSL in the same way. libIGCM include a master job and auxilary jobs for post-treatements. libIGCM is documented in the platform/documentation mentioned above.

Basic ORCHIDEE offline scripts

The trunk version of the scripts are under developement. Follow here the latest modifications.

ORCHIDEE for CMIP5 and trunk (beginning of 2011) has three off-line drivers :

  1. orchidee_ol that use all ORCHIDEE source (dim2_driver, SECHIBA, STOMATE and LPJ) and may run the full ORCHIDEE model or just a part of (juste the driver and SECHIBA with prescibe LAI).
  2. teststomate is the driver to run only STOMATE and LPJ part of the model (daily). It is used to accelerate the SPINUP of the vegetation (but without feedback to the physic : soil temperature, hydrology).
  3. forcesoil is the driver to accelerate the convergence of the soil carbon pools only.

There are four basic directories (configuration) to run ORCHIDEE in a simple mode :

  1. OOL_SEC: used to run orchidee_ol without STOMATE and LPJ (SECHIBA with prescibe LAI).
  2. OOL_SEC_STO : run orchidee_ol with the full ORCHIDEE model.
  3. TESTSTOMATE : run teststomate and only STOMATE and LPJ part of the model
  4. FORCESOIL : run forcesoil to converge the soil carbon pools.

Each of those directories contains :

  • a config.card file to describe the configuration (see JobName, LongName, TagName, CalendarType, ListOfComponents), the experiment specifications (!Restarts and !Post) and informatic parameters (parallelization, WriteFrequency).
  • in COMP directory, you may find "card" and "driver" files for each components list in ListOfComponents section of config.card.
  • in PARAM directory you may find default parameters files for each components. It gives a list of all parameters required by the model with the routine "getin". Those files contains only default parameters (documented). You may change them with care because it can give an eratic behaviour of the model and some parameters are changed automaticly by the script (see remark 2 below).
  • Finaly, POST directory gives configurations files for SECHIBA and STOMATE/LPJ component outputs. Please, see intranet wiki page on Monitoring, if you want to add your own variables in MONITORING web pages. See remark 3.

Some important remarks :

  1. The type of the calendar (CalendarType) and the dates (DateBegin and DateEnd) are only use by the scripts to get the right input (forcings, maps ...) files, but they are not passed to the model. For ORCHIDEE model, the forcing file must give all informations on the calendar.
  2. The options in the cards always gives priority parameters regards to those of the parameter files because the driver use those options to overwrite the parameter value in the last input parameter files in the RUN_DIR directory.
  3. You may add you own TS (TimeSeries) monitoring in your DODS web page for your simulations. For that, you must verify that the variable is correctly output (right histdef and histwrite are created and calls in your version of the source code). You must control that the variable is listed in the TimeSeriesVars option (2D or 3D list depends on the dimension of the variables) in the Post_1M_"your_component_history_file" section. Then it will be automaticly created if you have add the right line in your POST component file (with cfg extension).


ORCHIDEE_OL/SPINUP is not longer maintained!!! We no advise to use OOL_SEC_STO with spinup analytic, see HowTo/SpinupInJobBasic.

Spin-up are the algorithms to get the convergence of a part of the surface model. They are used to give correct initial state for historical simulations.

The equilibrium of the physic (SECHIBA) of the land surface should be reach in less than 10 years with a fix climatology and a prescribe LAI. You may take care of the year of the forcing file because Nino or Nina specific year may give bad results for global spin-up.

The equilibrium of the LAI (seasonnal variation of the vegetation) less than take two decade to converge. There is a big feedback between the LAI and the hydrology and energy budget.

But the soil carbon pools take thousand of years to converge, but there is no feedback between those pools and the LAI and the hydrology yet.

important remark :
This configuration use OOL_SEC, OOL_SEC_STO, TESTOMATE, FORCESOIL basic configurations as skeletons to launch each spinup stages, depends of the algorithm you have chosen.
You may not change those initial directories (or with great care) because it may change all your spin-up !

See page SpinUpJobs for additionnal informations.

ENSEMBLE configuration

With this configuration, you can change the forcing files and all parameters (by vegetation - PFTs - or not) to build all ENSEMBLE experiments you want with ORCHIDEE model.

For each experiment, this configuration will use the SPINUP configuration as a skeleton to launch a set of jobs.

This ENSEMBLE configuration can be used for setting an ensemble of simulations over different FLUXNET sites. In this case, the vegetation repartition has to be prescribed. It provides a performent tool to validate ORCHIDEE model on a grid of sites (one point for each simulation) all over the world. It give fast spinup and simulation on a various set of vegetation and climate distributions. See page FluxnetValidation for a complete documentation on FLUXNET sites validations.