Changes between Version 8 and Version 9 of Scripts/SpinUpJobs
- Timestamp:
- 2020-02-28T15:51:58+01:00 (4 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Scripts/SpinUpJobs
v8 v9 1 2 = Documentation on spin-up job with libIGCM = 1 = Documentation on SPINUP job with libIGCM = 2 Last revision: 2020/02/28, F. Maignan 3 3 4 4 == User documentation == 5 6 This page gives a short documentation on the spin-up job in ORCHIDEE_OL 5 This page gives a short documentation on the SPINUP configuration in ORCHIDEE_OL 7 6 sources since OOL_1_9_2 version. 8 7 9 If you just want to run a simple job without spin-up scheme you should copy the entire directory to another name and work inside the new one. For 10 example for ORCHIDEE_OL : 11 {{{ 12 > cp -Rp OOL_SEC_STO MY_OOL_SEC_STO 13 > cd MY_OOL_SEC_STO 14 }}} 15 16 17 The ORCHIDEE_OL/SPINUP script use other libIGCM scripts in ORCHIDEE_OL. 18 You should also copy this directory to another name and work inside the new one : 8 The ORCHIDEE_OL/SPINUP script uses other libIGCM scripts in ORCHIDEE_OL. 9 You should copy this directory to another name and work inside the new one: 19 10 {{{ 20 11 > cp -Rp SPINUP MY_SPINUP … … 23 14 24 15 25 Other ORCHIDEE_OL directories may not be modified for the SPINUP to run correctly 16 Other ORCHIDEE_OL directories may not be modified for the SPINUP to run correctly: 26 17 * OOL_SEC for SECHIBA alone runs, 27 18 * OOL_SEC_STO for SECHIBA and STOMATE (whole ORCHIDEE) runs, 28 19 * TESTSTOMATE for teststomate (STOMATE alone) runs, 29 20 * and FORCESOIL for forcesoil (stomate_soilcarbon function in src_stomate) runs. 30 All those s will be called "subjob" inside the spinup. They will are copy inside the spinupdirectory31 with different estage names. Some of their parameters will be changed according to the spinup parameters.32 And will be launched with a simple "nohup".21 All those will be called "subjob" inside the spinup. They will all be copied under the SPINUP directory 22 with different stage names. Some of their parameters will be changed according to the spinup parameters. 23 And they will be launched with a simple "nohup". 33 24 34 Then all these directories must be considered by users as skeleton and must be use or changewith25 Then all these directories must be considered by users as skeleton and must be used or changed with 35 26 care because otherwise, it will break the spinup. 36 The SPINUP directory itself is a brick of other jobs (see FluxnetValidation page on this site.27 The SPINUP directory itself is a brick of other jobs (see also the Fluxnet Validation page on this site). 37 28 38 29 In SPINUP/COMP directory, you will find spinup.card to manage SPINUP with ORCHIDEE in libIGCM scripts environment. 39 30 40 31 First, you must consider SPINUP configuration in section [User``Choices] : 41 * The first two options are 32 * The first two options are: 42 33 {{{ 43 34 #!sh … … 79 70 duree_final=1 80 71 }}} 72 81 73 Here the first three parameters deal with the initialization, if you don't want to start it from some restart. 82 74 After that, you have the main loop on "n_iter" and at the end the finalization of the spinup. [[BR]] 83 75 All those parameters (but the n_iter) are number of years. 84 * Finally, you can change 85 * The name of the forcing file. You can for example use ${year} variable of libIGCM to build interanual spinup as in 76 * Finally, you can change: 77 * The name of the forcing file. You can for example use ${year} variable of libIGCM to build interanual spinup as in: 86 78 {{{ 87 79 #!sh … … 91 83 ListNonDel= () 92 84 }}} 93 * Some parameters inside the subjobs .85 * Some parameters inside the subjobs: 94 86 {{{ 95 87 #!sh … … 99 91 LONGPRINT=n 100 92 }}} 101 * The post-treatment section for SECHIBA and STOMATE runs (Time``Series variables) 93 * The post-treatment section for SECHIBA and STOMATE runs (Time``Series variables): 102 94 {{{ 103 95 #!sh … … 113 105 114 106 115 == Directories of spin -up job ==107 == Directories of spinup job == 116 108 117 109 SPINUP for ORCHIDEE is a set of jobs running SEQUENTIALLY.
