Changes between Version 1 and Version 2 of DocScripts
- Timestamp:
- 2011-06-27T12:56:25+02:00 (13 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
DocScripts
v1 v2 2 2 3 3 When you have installed ORCHIDEE and ORCHIDEE_OL source code for trunk version as 4 described in the [http://dods.ipsl.jussieu.fr/orchidee/Cours-ORCHIDEE-mai2011.pdf 5 course],you will find in "modipsl"/config/ORCHIDEE_OL tree some directories for4 described in the [http://dods.ipsl.jussieu.fr/orchidee/Cours-ORCHIDEE-mai2011.pdf course], 5 you will find in "modipsl"/config/ORCHIDEE_OL tree some directories for 6 6 scripts used to run ORCHIDEE in an off-line mode. 7 7 … … 9 9 one : 10 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] 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. 12 13 1. [http://forge.ipsl.jussieu.fr/libigcm libIGCM] users and developpers documentation. 13 14 Some of those documentations are still in french and deal with the global couple … … 17 18 18 19 Other documentations can be found in other page of this wiki site : 19 * [wiki: FluxnetValidation]20 * [wiki:S pinUpJobs]20 * [wiki:Scripts/FluxnetValidation] 21 * [wiki:Scripts/SpinUpJobs] 21 22 22 23 Remark : there is a copy of all ORCHIDEE script directories in model/ORCHIDEE_OL. … … 47 48 48 49 There are four basic directories (configuration) to run ORCHIDEE in a simple mode : 49 1. OOL_SEC: used to run orchidee_ol without STOMATE and LPJ (SECHIBA with prescibe50 1. [source:trunk/ORCHIDEE_OL/OOL_SEC OOL_SEC]: used to run orchidee_ol without STOMATE and LPJ (SECHIBA with prescibe 50 51 LAI). 51 1. OOL_SEC_STO: run orchidee_ol with the full ORCHIDEE model.52 1. TESTSTOMATE: run teststomate and only STOMATE and LPJ part of the model53 1. FORCESOIL: run forcesoil to converge the soil carbon pools.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. 54 55 55 56 Each of those directories contains : … … 59 60 * in COMP directory, you may find "card" and "driver" files for each components list 60 61 in !ListOfComponents section of config.card. 61 * 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 62 72 63 73 Some important remarks : 64 *The type of the calendar (!CalendarType) and the dates (!DateBegin and !DateEnd) are74 1. The type of the calendar (!CalendarType) and the dates (!DateBegin and !DateEnd) are 65 75 only use by the scripts to get the right input (forcings, maps ...) files, but they 66 76 are not passed to the model. For ORCHIDEE model, the forcing file must give 67 77 all informations on the calendar. 68 * The options in the cards are always '''prioritary''' (????) onthose of the69 parameter files because the driver use those cardoptions to overwrite the78 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 70 80 parameter value in the last input parameter files in the RUN_DIR directory. 71 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). 72 88 73 89 == SPINUP job == … … 81 97 global spin-up. 82 98 83 See page [wiki:SpinUpJobs] for additionnal informations. 99 The equilibrium of the LAI (seasonnal variation of the vegetation) less than take two 100 decade to converge. There is a big feedback between the LAI and the hydrology and 101 energy budget. 102 103 But the soil carbon pools take thousand of years to converge, but there is no 104 feedback between those pools and the LAI and the hydrology yet. 105 106 '''important remark :''' [[BR]] 107 This configuration use OOL_SEC, OOL_SEC_STO, TESTOMATE, FORCESOIL basic 108 configurations as skeletons to launch each spinup stages, depends of the algorithm 109 you have chosen. [[BR]] 110 You may not change those initial directories (or with great care) because it may 111 change all your spin-up ! 112 113 See page [wiki:Scripts/SpinUpJobs] for additionnal informations. 84 114 85 115 == FLUXNET job == 86 116 117 FLUXNET forcing files give a performent tool to validate ORCHIDEE model on a grid of 118 sites (one point for each simulation) all over the world. It give fast spinup and 119 simulation on a various set of vegetation and climate distributions. 120 121 This configuration use SPINUP configuration as a skeleton to launch an ensemble of 122 jobs over the selected sites in FLUXNET or LATHUILE input files. 123 124 For FLUXNET jobs, the vegetation repartition is prescribed. Then default parameter 125 IMPOSE_VEG is automaticly set to 'y' and the veget_max must be given in the list for 126 each sites. 127 128 See page [wiki:Scripts/FluxnetValidation] for a complete documentation on FLUXNET sites validations. 129 87 130 == ENSEMBLE job == 131 132 ENSEMBLE configuration give a generalization of FLUXNET sites script to run global 133 ENSEMBLE spinup and experiments. 134 135 With this configuration, you can change the forcing files and all parameters (by 136 vegetation - PFTs - or not) to build all ENSEMBLE experiments you want with ORCHIDEE 137 model. 138 139 This scripts give the same tools as FLUXNET configuration, but there is no IMPOSE_VEG 140 set (initial vegetation is not prescribed).