Changes between Version 7 and Version 8 of Documentation/UserGuide/ManipulationDefFile

Timestamp:

2020-02-28T11:45:42+01:00 (4 years ago)

Author:

bguenet

Comment:

--

Documentation/UserGuide/ManipulationDefFile

@@ -24 +24 @@
 
 * ''nonblocker parameter'' can be modified or removed from run.def.
-Example ''nonblocker'' parameter, extract from PARAM/run.def in ORCHIDEE_OL/OOL_SEC_STO:
+Example ''nonblocker'' parameter, extract from PARAM/run.def in ORCHIDEE_OL/OOL_SEC_STO_FG2:
 {{{
 # SECHIBA history output level (0..10)
@@ -33 +33 @@
 
 * ''blocker parameter'' can not be modified or removed from run.def otherwise the job will stop before executing the model. 
-Example, extract from PARAM/run.def in ORCHIDEE_OL/OOL_SEC_STO:
+Example, extract from PARAM/run.def in ORCHIDEE_OL/OOL_SEC_STO_FG2:
 {{{
 # Name of restart to read for initial conditions of STOMATE
 STOMATE_RESTART_FILEIN = _AUTOBLOCKER_
 }}}
-The variable STOMATE_RESTART_FILEIN is set changed due to restart options set in config.card. It is an important parameter and is therefore a so called ''blocker parameter''. If a blocker parameter is changed, the job will stop before launching the model. For example if it is set to STOMATE_RESTART_FILEIN=stomate_rest_in.nc, then the job will stop. This parameter must contain the key word AUTO.  
+The variable STOMATE_RESTART_FILEIN is set changed due to restart options set in config.card. It is an important parameter and is therefore a so called ''blocker parameter''. If a blocker parameter is changed, the job will stop before launching the model. For example if it is set to STOMATE_RESTART_FILEIN=stomate_rest_in.nc, then the job will stop. This parameter must contain the key word AUTO. Except if you really know what you are doing we do not advice to modify the blocker parameters.  
 
 
 '''Implementation'''[[BR]]
+If you added ''nonblocker'' or ''blocker'' parameters (i.e. those identified by AUTO or AUTOBLOCKER in the run.def) you must be sure that they are read and modified by the .driver files following the instructions below
+
+
 The component's driver call the libIGCM function IGCM_comp_modifyDefFile (for run.def, orchidee.def,... ) or IGCM_comp_modifyXmlFile (for xml files) for each variable that needs to be manipulated.