Changes between Version 1 and Version 2 of Documentation/UserGuide/Config


Ignore:
Timestamp:
2011-10-07T17:03:53+02:00 (11 years ago)
Author:
nvuilsce
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • Documentation/UserGuide/Config

    v1 v2  
    1 aaa 
     1= Documentation for ORCHIDEE_OL scripts = 
     2 
     3When you have installed ORCHIDEE and ORCHIDEE_OL source code for trunk version as 
     4described in the [http://dods.ipsl.jussieu.fr/orchidee/Cours-ORCHIDEE-mai2011.pdf course],  
     5you will find in "modipsl"/config/ORCHIDEE_OL tree some directories for 
     6scripts used to run ORCHIDEE in an off-line mode.  
     7 
     8We strongly invite you to read other wiki and pdf documentation in addition of this 
     9one : 
     10 1. [http://forge.ipsl.jussieu.fr/igcmg/wiki/ModipslBeginner ModipslBeginner] 
     11 1. [http://forge.ipsl.jussieu.fr/igcmg/wiki/igcmg/Documentation Documentation for IPSLCM5 current release of IPSL coupled model]  
     12    gives a lot of links on other documentations.  
     13 1. [http://forge.ipsl.jussieu.fr/libigcm libIGCM] users and developpers documentation. 
     14Some of those documentations are still in french and deal with the global couple 
     15model of IPSL (namly IPSLCM5 for CMIP5 exercise). But ORCHIDEE scripts use the same 
     16philosophy for executions, tree of directories, etc... 
     17 
     18 
     19Other documentations can be found in other page of this wiki site :  
     20 * [wiki:FluxnetValidation] 
     21 * [wiki:SpinUpJobs] 
     22 
     23Remark : there is a copy of all ORCHIDEE script directories in model/ORCHIDEE_OL. 
     24This is for subversion management and it won't work correctly if you use those 
     25directories. You must use ones in config/ORCHIDEE_OL. 
     26 
     27== libIGCM scripts == 
     28 
     29libIGCM scripts are used as an SRE (Sytem Running Environment). They are used to 
     30manipulate input and output files for an executable (or a set of executables in the 
     31couple configuration). 
     32• libIGCM : Set of scripts to launch simulations and posttreat. Modularity and 
     33portability make you jobs work on a lot of machine (super-computer) in the same way.  
     34• Include a master job and a lot of auxilary jobs for post-treatements. 
     35• Documentation : http://forge.ipsl.jussieu.fr/libigcm 
     36 
     37== Basic ORCHIDEE scripts == 
     38 
     39ORCHIDEE for CMIP5 and trunk (beginning of 2011) has three off-line drivers : 
     40 1. orchidee_ol that use all ORCHIDEE source (dim2_driver, SECHIBA, STOMATE and LPJ) 
     41    and may run the full ORCHIDEE model or just a part of (juste the driver and SECHIBA 
     42    with prescibe LAI). 
     43 1. teststomate is the driver to run only STOMATE and LPJ part of the model (daily). 
     44    It is used to accelerate the SPINUP of the vegetation (but without feedback to 
     45    the physic : soil temperature, hydrology). 
     46 1. forcesoil is the driver to accelerate the convergence of the soil carbon pools 
     47    only. 
     48 
     49There are four basic directories (configuration) to run ORCHIDEE in a simple mode : 
     50 1. [source:trunk/ORCHIDEE_OL/OOL_SEC OOL_SEC]: used to run orchidee_ol without STOMATE and LPJ (SECHIBA with prescibe 
     51    LAI). 
     52 1. [source:trunk/ORCHIDEE_OL/OOL_SEC_STO OOL_SEC_STO] : run orchidee_ol with the full ORCHIDEE model. 
     53 1. [source:trunk/ORCHIDEE_OL/TESTSTOMATE TESTSTOMATE] : run teststomate and only STOMATE and LPJ part of the model  
     54 1. [source:trunk/ORCHIDEE_OL/FORCESOIL FORCESOIL] : run forcesoil to converge the soil carbon pools. 
     55 
     56Each of those directories contains : 
     57 * a config.card file to describe the configuration (see !JobName, !LongName, 
     58   !TagName, !CalendarType, !ListOfComponents), the experiment specifications 
     59   (!Restarts and !Post) and informatic parameters (parallelization, !WriteFrequency).  
     60 * in COMP directory, you may find "card" and "driver" files for each components list 
     61   in !ListOfComponents section of config.card. 
     62 * in PARAM directory you may find default parameters files for each components. It 
     63   gives a list of all parameters required by the model with the routine "getin". 
     64   Those files contains only default parameters (documented). You may change them with 
     65   care because it can give an eratic behaviour of the model and some parameters are 
     66   changed automaticly by the script (see remark 2 below). 
     67 * Finaly, POST directory gives configurations files for SECHIBA and STOMATE/LPJ 
     68   component outputs. Please, see intranet wiki page on  
     69   [http://wiki.ipsl.jussieu.fr/IGCMG/Outils/ferret/Monitoring Monitoring], if you 
     70   want to add your own variables in MONITORING web pages. See remark 3. 
     71 
     72 
     73Some important remarks : 
     74 1. The type of the calendar (!CalendarType) and the dates (!DateBegin and !DateEnd) are 
     75   only use by the scripts to get the right input (forcings, maps ...) files, but they 
     76   are not passed to the model. For ORCHIDEE model, the forcing file must give 
     77   all informations on the calendar. 
     78 1. The options in the cards always gives priority parameters regards to those of the 
     79   parameter files because the driver use those options to overwrite the 
     80   parameter value in the last input parameter files in the RUN_DIR directory.     
     81 1. You may add you own TS (!TimeSeries) monitoring in your DODS web page for your 
     82   simulations. For that, you must verify that the variable is correctly output 
     83   (right histdef and histwrite are created and calls in your version of the source 
     84   code). You must control that the variable is listed in the TimeSeriesVars option 
     85   (2D or 3D list depends on the dimension of the variables) in the Post_1M_"your_component_history_file" 
     86   section. Then it will be automaticly created if you have add the right line in 
     87   your POST component file (with cfg extension). 
     88 
     89== SPINUP job == 
     90 
     91Spin-up are the algorithms to get the convergence of a part of the surface model. 
     92They are used to give correct initial state for historical simulations. 
     93 
     94The equilibrium of the physic (SECHIBA) of the land surface should be reach in less 
     95than 10 years with a fix climatology and a prescribe LAI. You may take care of the 
     96year of the forcing file because Nino or Nina specific year may give bad results for 
     97global spin-up. 
     98 
     99The equilibrium of the LAI (seasonnal variation of the vegetation) less than take two 
     100decade to converge. There is a big feedback between the LAI and the hydrology and 
     101energy budget. 
     102 
     103But the soil carbon pools take thousand of years to converge, but there is no 
     104feedback between those pools and the LAI and the hydrology yet. 
     105 
     106'''important remark :''' [[BR]] 
     107This configuration use OOL_SEC, OOL_SEC_STO, TESTOMATE, FORCESOIL basic 
     108configurations as skeletons to launch each spinup stages, depends of the algorithm 
     109you have chosen. [[BR]] 
     110You may not change those initial directories (or with great care) because it may 
     111change all your spin-up !  
     112 
     113See page [wiki:SpinUpJobs] for additionnal informations. 
     114 
     115== FLUXNET job == 
     116 
     117FLUXNET forcing files give a performent tool to validate ORCHIDEE model on a grid of 
     118sites (one point for each simulation) all over the world. It give fast spinup and 
     119simulation on a various set of vegetation and climate distributions.   
     120 
     121This configuration use SPINUP configuration as a skeleton to launch an ensemble of 
     122jobs over the selected sites in FLUXNET or LATHUILE input files.   
     123 
     124For FLUXNET jobs, the vegetation repartition is prescribed. Then default parameter 
     125IMPOSE_VEG is automaticly set to 'y' and the veget_max must be given in the list for 
     126each sites.  
     127 
     128See page [wiki:FluxnetValidation] for a complete documentation on FLUXNET sites validations. 
     129 
     130== ENSEMBLE job == 
     131 
     132ENSEMBLE configuration give a generalization of FLUXNET sites script to run global 
     133ENSEMBLE spinup and experiments. 
     134 
     135With this configuration, you can change the forcing files and all parameters (by 
     136vegetation - PFTs - or not) to build all ENSEMBLE experiments you want with ORCHIDEE 
     137model. 
     138 
     139This scripts give the same tools as FLUXNET configuration, but there is no IMPOSE_VEG 
     140set (initial vegetation is not prescribed).