Launching a suite of simulations with the Job_ENSEMBLE script

Job_ENSEMBLE helps at running a suite of simulations of ORCHIDEE. It may be used for running ORCHIDEE at Fluxnet sites or for performing different simulations with different parametrizations, ... Typically, we can configure the length of each type of simulations (initialisation, full orchidee, teststomate, forcesoil, final) and the number of times we iterate on (full orchidee, teststomate, forcesoil).

In addition, for each simulation, the user can re-specify any "paremeter" he/she wants (PFT-dependant or not).

Where is Job_ENSEMBLE located ?

Job_ENSEMBLE is under modipsl/config/ORCHIDEE_OL/ENSEMBLE dir.

What does ENSEMBLE dir contain ?

• config.card : information on Job Name, Tag Name, Dates and Restart.
• fluxnet.card and ensemble.card configure the list of FLUXNET sites or of simulations (type and associated parameters)
• PARAM/run.def, the parameter file of ORCHIDEE
• atlas_FLUXNET_V1.cfg and atlas_FLUXNET_taylor.cfg (used for the post-treatment)
• taylor_arrow_fluxnet_final_1.jnl, taylor_arrow_fluxnet_final_2.jnl and ORCHIDEE_3diff.jnl (used for the post-treatment)
• The script "install"
• The scripts ensemble.ksh and post_FLUXNET
• run.card.init

How to install Job_ENSEMBLE ?

• If not done yet, first type under "util" (now in "libIGCM") dir :

  my_prompt>> ./ins_job 
  

  It will create Job_Sp (where Sp is the Job Name specified in config.card)
• Then, to update Job_ENSEMBLE and Job_Post_FLUXNET (used for the post-treatment), under "ENSEMBLE" dir type

  my_prompt>> ./install
  

DSG remark: the script "./install" doesn't exist anymore with recent code (02/2016)

How to configure the Job_ENSEMBLE_validation script

In order to configure the script, you need to fill the fluxnet.card or ensemble.card file.

Standard parameters to be filled into fluxnet.card

• ForcingsPath specifies the location where are stored the meteorological input files for each FLUXNET site.
• NbSitesParam specifies the number of parameters to modify per PFT for each site
• NameSitesParam specifies the name of the parameters to modify per PFT for each site (as it appears in the .def files)
• CompSitesParam specifies the name of the component for each parameter described in NameSitesParam (either, SECHIBA, STOMATE, or DRIVER)
• Sites is a list of parameter values fill for each FLUXNET sites or each simulation. The four first parameters are Name (used as site Id), Forcing file (files stored being Fluxnetpath being of the type "Forcing file".nc), Initial Year, Number of years in forcing file. The following parameters are those defined by NameSitesParam. Alternatively to the use of the Sites parameter, you can define several groups of sites. Each group is defined as the Sites parameter. The name of the groups are defined by the user. Then each group as to be listed in a parameter named Groups. The default setting of the fluxnet.card makes use of the Groups parameter.
• Initial step: set to a positive value either "duree_nostomate" (initialisation without stomate component), "duree_inistomate" (initialisation with stomate component) or "duree_offlineini" (initialisation with teststomate)
• Loop over ORCHIDEE runs:
  • n_iter, the whole job is restarted n_iter times
  • duree_sechiba, orchidee with sechiba (and stomate if ok_stomate=y below)
  • duree_stomate, length of teststomate runs
  • duree_carbonsol, length of forcesoil runs
• Final step: specify the length of the final run with the parameter "duree_final"
• Under the [UserChoices] section, the user specifies the main configurations of ORCHIDEE
  • To activate/desactivate stomate => ok_stomate=y/n
  • To activate/desactivate photosynhesis calculation => ok_co2=y/n
  • To activate/desactivate the new hydrology scheme (deRosnay) => ok_newhydrol=y/n
• Under the [SubJobParams] section, the user can specify any parameter to be modified in sechiba.def, stomate.def or driver.def

Optional parameters

Option CONSERVE

If you want to keep the history files of all simulations ran by the Job_FLUXNET_Validation script, set to yes (CONSERVE=y) the flag CONSERVE, else set it to no (CONSERVE=n).

How to use it ?

For a set of ENSEMBLE simulations

my_prompt>> ksh
my_prompt>> nohup ./Job_ENSEMBLE ensemble > out_Job 2>&1 &

For a set of FLUXNET simulations

my_prompt>> ksh
my_prompt>> nohup ./Job_ENSEMBLE fluxnet > out_Job 2>&1 &