1 | OBJECTIVE: This Readme describes how to use the Make_orchidee_pft.py |
---|
2 | script to generate an orchidee_pft.def_xxpft.xxac file. |
---|
3 | |
---|
4 | BACKGROUND. The model now requires 3 different def files: |
---|
5 | 1 - run.def contains the settings that are specific for the driver: |
---|
6 | off-line or coupled. |
---|
7 | 2 - orchidee.def contains the settings that are specific for an |
---|
8 | experiment. The same orchidee.def file can be used in off-line |
---|
9 | and coupled mode |
---|
10 | 3 - orchidee_pft.def contains the PFT specific settings. The same |
---|
11 | settings can be used across experiments and drivers. Nevertheless, |
---|
12 | different PFT maps may require different orchidee_pft.defs. |
---|
13 | |
---|
14 | SYNTAX: The script Make_orchidee_pft_defs.py is the main script and |
---|
15 | should be run in python. |
---|
16 | > module load python |
---|
17 | > python Make_orchidee_pft_defs.py |
---|
18 | |
---|
19 | The script will ask for a revision number. This revision number can be |
---|
20 | provided through the terminal or it can be given through an arguments |
---|
21 | at the time the script is ran: |
---|
22 | > python Make_orchidee_pft_defs.py -rev XXXX |
---|
23 | or |
---|
24 | > python Make_orchidee_pft_defs.py -r XXXX |
---|
25 | |
---|
26 | MAIN SCRIPT: Make_orchidee_pft_defs.py. The main script is currently |
---|
27 | set up to make 4 different orchidee_pft.defs All 4 orchidee_pft.defs |
---|
28 | will be copied in the 8 experiment folders (ENSEMBLE, OOL_SEC, |
---|
29 | OOL_SEC_STO_FG1trans, OOL_SEC_STO_FG2, OOL_SEC_STO_FG3, |
---|
30 | OOL_SEC_STO_FG3nd, SPINUP, and SPINUP_ANALYTIC_FG1. |
---|
31 | |
---|
32 | The main script makes use of the processed parameter file. This file |
---|
33 | contains an archive of all parameter values used in different versions |
---|
34 | of ORCHIDEE-CN-CAN (see PARAMETERS below). Likewise the script |
---|
35 | requires files that describe the PFT configuration in terms of the |
---|
36 | pfts that should be used and the number of age classes (see |
---|
37 | CONFIGURATIONS below). |
---|
38 | |
---|
39 | If the script has to be extended for other experiments the folder name |
---|
40 | has to be added to the variable 'experiments'. If the orchidee_pft.def |
---|
41 | needs to be produced for another PFT configuration the configuration |
---|
42 | file will have to be prepared and the main script will have to be |
---|
43 | adjusted in the section 'Get the configuration of the PFTs'. First |
---|
44 | adjuest the rang(0,4) right above this section. Next add another elif |
---|
45 | in the section. The rest of the script can be left untouched. |
---|
46 | |
---|
47 | The script will ask you to give the orchidee revision number for which you want |
---|
48 | to make the run.defs. The script works of course for the latest ORCHIDEE revision but |
---|
49 | if all correctly filled out the different tables, the script was set up to generate |
---|
50 | the correct run.defs for previous versions as well. The oldest tested version it can |
---|
51 | go back to is r5800. |
---|
52 | |
---|
53 | |
---|
54 | PARAMETERS: processes_parameters.py |
---|
55 | This tables contain a single line per PFT and per parameter. If a model version |
---|
56 | requires a new parameter value, add a line with the correct date, revision number |
---|
57 | and parameter value. When adding new parameters names to the table make a note in |
---|
58 | the table called added. If a parameter is no longer needed after a revision than add |
---|
59 | that parameetr name and the revision number to the table called |
---|
60 | removed. NEVER DELETE OR ADJUST A PARAMETER ENTRY FROM THIS TABLE! |
---|
61 | This table is our archive - only add new entries. If a new PFT has |
---|
62 | been parameterized, add all parameter values to this table. |
---|
63 | |
---|
64 | |
---|
65 | CONFIGURATIONS: configuration.py |
---|
66 | The configuration_template.py contains all the PFTs for which ORCHIDEE-CN-CAN has been |
---|
67 | parameterized. Add new PFTs to this table. When making a new configuration file copy the |
---|
68 | template and save it as a new file. Delete the PFTs that should not appear in your PFT |
---|
69 | configuration. Specify the number of age classes and mark for each PFT whether it |
---|
70 | should be run with age classes or not. There is no need to change the current 4 |
---|
71 | configuration files. New files can be added to the main script (see above) and old |
---|
72 | configuration files should no longer be called by the main script. DO |
---|
73 | NOT DELETE OR OVERWRITE CONFIGURATION FILES! Those files are part of our archive. |
---|
74 | |
---|
75 | |
---|
76 | |
---|
77 | |
---|
78 | |
---|
79 | |
---|
80 | |
---|
81 | |
---|
82 | |
---|
83 | |
---|