Context Navigation

CheckList

Timestamp:: 2020-06-03T18:11:31+02:00 (4 years ago)
Author:: luyssaert
Comment:: --

Legend:

: Unmodified
: Added
: Removed
: Modified

Documentation/UserGuide/CheckList

-                      v38
+                      v39
 '''4a) The simplest option is to use predefined libIGCM configuration  '''
 Several of these configurations are used in the [wiki:ReferenceSimulations reference simulations], each corresponding to a different [https://forge.ipsl.jussieu.fr/igcmg_doc/wiki/Doc/Setup#Contentsofthesubmissiondirectory submission directory] in modipsl/config/ORCHIDEE_OL/. A detailed description of each of these configurations is listed [https://forge.ipsl.jussieu.fr/orchidee/wiki/Documentation/TrunkFunctionality4#Configurationsr6614 here]
+Several of these configurations are used in the [wiki:ReferenceSimulations reference simulations], each corresponding to a different [https://forge.ipsl.jussieu.fr/igcmg_doc/wiki/Doc/Setup#Contentsofthesubmissiondirectory submission directory] in modipsl/config/ORCHIDEE_OL/. A detailed description of each of these configurations is listed [https://forge.ipsl.jussieu.fr/orchidee/wiki/Documentation/TrunkFunctionality4#Configurations here]
 - ENSEMBLE to run at FLUXNET sites
 - SPINUP_ANALYTIC_FG1, OOL_SEC_STO_FG1trans, OOL_SEC_STO_FG2, which are designed to be used one after the other to run a simulation with CRU-NCEP atmospheric forcing and the long spinup required for the carbon and nitrogen cycle ([wiki:Documentation/UserGuide/SpinUpCarbon#StandardprotocolforCarbon-relatedvariables more details])
 …
 - config.card => to choose the name, length, restart of your simulation ([https://forge.ipsl.jussieu.fr/igcmg_doc/wiki/Doc/Setup#config.card more details])
 - PARAM/run.def, PARAM/orchidee.def and PARAM/orchidee_pft.def => Prior to r6616 the information contained in these three files was combined in a single file called PARAM/run.def. Since r6616 three different files have been defined to better match what is being done in LMDzOR. The concept and many details on these three files can be found  [https://forge.ipsl.jussieu.fr/orchidee/wiki/Documentation/TrunkFunctionality4#Parameterfilesr6614 here]. The basic idea is that those files enable the users to choose the options of their simulation, via "keywords". These keywords can be a flag (y or n to activate them or not) or they can be parameters values that you can change without recompiling the model. The number of these keywords is huge, and it has a large effect on the outcome of your simulation. The default values depend on the revision (see 2). More details on [https://forge.ipsl.jussieu.fr/igcmg_doc/wiki/Doc/Setup#PARAMdirectory run.def] and see 4c for a list of keywords.
+- PARAM/run.def, PARAM/orchidee.def and PARAM/orchidee_pft.def => Prior to r6616 the information contained in these three files was combined in a single file called PARAM/run.def. Since r6616 three different files have been defined to better match what is being done in LMDzOR. The concept and many details on these three files can be found  [https://forge.ipsl.jussieu.fr/orchidee/wiki/Documentation/TrunkFunctionality4#Parameterfiles here]. The basic idea is that those files enable the users to choose the options of their simulation, via "keywords". These keywords can be a flag (y or n to activate them or not) or they can be parameters values that you can change without recompiling the model. The number of these keywords is huge, and it has a large effect on the outcome of your simulation. The default values depend on the revision (see 2). More details on [https://forge.ipsl.jussieu.fr/igcmg_doc/wiki/Doc/Setup#PARAMdirectory run.def] and see 4c for a list of keywords.
 - COMP/orchidee_ol.card => defines the meteorological forcing files and xml files (the latter of which are only used with XIOS; ORCHIDEE can also be run [https://forge.ipsl.jussieu.fr/orchidee/wiki/Documentation/UserGuide/DeactivateXIOS without XIOS], though it is not recommended). The list of available atmospheric forcing datasets is regularly updated [wiki:Documentation/Forcings here].
 - COMP/sechiba.card => defines the other input files ([https://forge.ipsl.jussieu.fr/orchidee/wiki/Documentation/Ancillary list of available datasets]), and some important user option for sechiba:
 …
 - If it was libIGCM that crashed, carefully read the error log in the Script file. Most often it will be a trivial problem such as a typo in a file name or a path. Guidelines to understand the logs produced by libIGCM can be found  [https://forge.ipsl.jussieu.fr/igcmg_doc/wiki/Doc/CheckDebug here]
 - If it was ORCHIDEE that crashed and you were using a single processor simply rerun the model after compiling it in debug mode. The model will of crash again (but not necessarily in the same place because PROD will not crash on divide by zero where DEBUG will crash) and will get an error-stack. This stack will tell you in which line the model crashed. The line number refers to some processed files that can be found in modeles/ORCHIDEE/build/ppcr/... but as a rule of thumb you need to subtract 9 lines from the error stack to get the correct line number in modeles/ORCHIDEE/scr_*/*.f90.
 - You can also make use of [https://forge.ipsl.jussieu.fr/orchidee/wiki/Documentation/TrunkFunctionality4#Consistencychecksr6614 the internal consistency checks] (starting r6616) to get an idea where the model crashes.
+- You can also make use of [https://forge.ipsl.jussieu.fr/orchidee/wiki/Documentation/TrunkFunctionality4#Consistencychecks the internal consistency checks] (starting r6616) to get an idea where the model crashes.
 - If the above options does not reveal the problem some serious debugging will be required. Look at the [wiki:Documentation/UserGuide#Debuggingandprofiling Debugging section] on the [https://forge.ipsl.jussieu.fr/orchidee/wiki/Documentation/UserGuide HowTo], starting with the [wiki:Documentation/UserGuide/flags introductory page on debug flags].
 - The [https://forge.ipsl.jussieu.fr/igcmg_doc/wiki/Doc/Setup#config.card TEST and DEVT options in config.card] can be useful as they keep more log files accessible