Changes between Version 4 and Version 5 of Scripts/Ensemble

Timestamp:

2013-09-26T16:18:25+02:00 (11 years ago)

Author:

nvuilsce

Comment:

--

Scripts/Ensemble

@@ -1 @@
-= Launching a suite of simulations with Job_FLUXNET_validation script  =
-Job_FLUXNET_validation helps at running a suite of simulations ORCHIDEE over several Fluxnet sites. 
+= 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).
 [[Image(http://dods.ipsl.jussieu.fr/orchidee/WIKI/flowchart_2.png)]][[BR]]
-In addition, for each FLUXNET site, the user can re-specify any "paremeter" he want (the main parameter to define being VEG_MAX).
+In addition, for each simulation, the user can re-specify any "paremeter" he/she wants (PFT-dependant or not).
 
-= Where is Job_FLUXNET_validation located ? =
-Job_FLUXNET_validation is under modipsl/config/ORCHIDEE_OL/FLUXNET dir.
+= Where is Job_ENSEMBLE located ? =
+Job_ENSEMBLE is under modipsl/config/ORCHIDEE_OL/ENSEMBLE dir.
 
-= What does FLUXNET dir contain ? =
+= What does ENSEMBLE dir contain ? =
  - '''config.card''' : information on Job Name, Tag Name, Dates and Restart.
- - '''fluxnet.card''' configures the list of FLUXNET sites (type and associated parameters)
- - PARAM/'''orchidee.def''', the parameter file of ORCHIDEE 
- - '''atlas_FLUXNET.cfg''' (used for the post-treatment)
+ - '''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 fluxnet.ksh and post_FLUXNET
+ - The scripts ensemble.ksh and post_FLUXNET
  - run.card.init
 
-= How to install Job_FLUXNET_validation ? =
+= How to install Job_ENSEMBLE ? =
  - If not done yet, first type under "util" dir :
 {{{ 
@@ -23 +24 @@
 }}}
  It will create Job_Sp (where Sp is the Job Name specified in config.card)
- - Then, to create Job_FLUXNET_validation and Job_Post_FLUXNET (used for the post-treatment), under "FLUXNET" dir type
+ - Then, to update Job_ENSEMBLE and Job_Post_FLUXNET (used for the post-treatment), under "ENSEMBLE" dir type
 {{{
 my_prompt>> ./install
 }}}
 
-= How to configure the Job_FLUXNET_validation script = 
-In order to configure the script, you need to fill the fluxnet.card file.
+= 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 ==
- - '''Fluxnet``Path''' specifies the location where are stored the meteorological input files for each FLUXNET site.
+ - '''Forcings``Path''' specifies the location where are stored the meteorological input files for each FLUXNET site.
  - '''Nb``Sites``Param''' specifies the number of parameters to modify per PFT for each site
  - '''Name``Sites``Param''' specifies the name of the parameters to modify per PFT for each site (as it appears in the .def files)
  - '''Comp``Sites``Param''' specifies the name of the component for each parameter described in Name``Sites``Param (either, SECHIBA, STOMATE, or DRIVER)
- - '''Sites''' is a list of parameter values fill for each FLUXNET sites.  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 Name``Sites``Param. 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.
+ - '''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 Name``Sites``Param. 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:
@@ -49 +50 @@
  - Under the [Sub``Job``Params] section, the user can specify any parameter to be modified in sechiba.def, stomate.def or driver.def
 
-== Optional parameters of fluxnet.card ==
+== Optional parameters ==
 
-=== Option CONSERVE into fluxnet.card ===
+=== 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_FLUXNET_validation > out_Job 2>&1 &
+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 &
 }}}
 
-= Requirement =
-On Obelix, you need to have a passphrase for connecting to obelix when launching automatically new jobs via ssh.[[BR]]
-From your home root directory:
-If the '.ssh' directory doesn't exist, create it.[[BR]]
-Then, go in this directory
-{{{
-my_prompt>> cd .ssh
-}}}
-Then, type:
-{{{
-my_prompt>> ssh-keygen -t rsa -N ""
-}}}
-Then,
-{{{
-my_prompt>> cp id_rsa.pub authorized_keys
-}}}
-or, if the file "authorized_keys" already exists:
-{{{
-my_prompt>> cat id_rsa.pub >> authorized_keys
-}}}