39 | | It consists of an overlayer of the current PFTs. Here is the list of the MTCs implemented in the ORCHIDEE "externalizes" version : |
| 46 | It consists of an overlayer of the current PFTs. Here is the list of the MTCs implemented in the ORCHIDEE "externalized" version : |
| 47 | |
| 48 | 1. bare ground |
| 49 | |
| 50 | 2. tropical broad-leaved evergreen |
| 51 | |
| 52 | 3. tropical broad-leaved raingreen |
| 53 | |
| 54 | 4. temperate needleleaf evergreen |
| 55 | |
| 56 | 5. temperate broad-leaved evergreen |
| 57 | |
| 58 | 6. temperate broad-leaved summergreen |
| 59 | |
| 60 | 7. boreal needleleaf evergreen |
| 61 | |
| 62 | 8. boreal broad-leaved summergreen |
| 63 | |
| 64 | 9. boreal needleleaf summergreen |
| 65 | |
| 66 | 10. C3 grass |
| 67 | |
| 68 | 11. C4 grass |
| 69 | |
| 70 | 12. C3 agriculture |
| 71 | |
| 72 | 13. C4 agriculture |
| 73 | |
| 74 | Actually, the MTCs match exactly to the usual PFTs. We only decided to put a new name for them.[[BR]] |
| 75 | We want to distinguish the floating number of PFTs from the fixed PFTs alias the MTCs. |
| 76 | |
| 77 | === How does it work? === |
| 78 | Basically, it will initialize all the pft-parameters by default values by linking a PFT to a MTC. [[BR]] |
| 79 | When you associate a PFT to a MTC, the parameters from this PFT will be initialized automatically by pre-defined |
| 80 | values. After that, you can impose any value you want for the parameters.[[BR]] |
| 81 | |
| 82 | === Why using the MTC? === |
| 83 | We tried to make ORCHIDEE more user-friendly with this version. In the current version of the externalized version, there is |
| 84 | approximatively 86 pfts-parameters of size 'nvm'. If the MTC didn't exist, the user has to fill the run.def file with 86*nvm |
| 85 | values! |
| 86 | |
| 87 | === Going back to our small problem === |
| 88 | |
| 89 | Now, we can solve our problem with the externalized version. The first step is to declare nvm, the number of PFTs you will |
| 90 | consider for your job.[[BR]] |
| 91 | |
| 92 | {{{ |
| 93 | NVM = 14 |
| 94 | }}} |
| 95 | |
| 96 | Here we consider 14 PFTs for solving our problem.[[BR]] |
| 97 | The second step is to fill an array called PFT_TO_MTC. PFT_TO_MTC is the correspondance table between PFT and MTC. |
| 98 | {{{ |
| 99 | PFT_TO_MTC__01 = 1 |
| 100 | PFT_TO_MTC__02 = 2 |
| 101 | PFT_TO_MTC__03 = 3 |
| 102 | PFT_TO_MTC__04 = 4 |
| 103 | PFT_TO_MTC__05 = 5 |
| 104 | PFT_TO_MTC__06 = 6 |
| 105 | PFT_TO_MTC__07 = 7 |
| 106 | PFT_TO_MTC__08 = 8 |
| 107 | PFT_TO_MTC__09 = 9 |
| 108 | PFT_TO_MTC__10 = 10 |
| 109 | PFT_TO_MTC__11 = 11 |
| 110 | PFT_TO_MTC__12 = 12 |
| 111 | PFT_TO_MTC__13 = 13 |
| 112 | PFT_TO_MTC__14 = 6 |
| 113 | }}} |
| 114 | |
| 115 | |
| 116 | Our first specie of tree is the PFT 6 and the second one, the PFT 14.[[BR]] |
| 117 | |
| 118 | They both belong to the MTC 6. The standard value for VCMAX for the MTC 6 is 15. [[BR]] |
| 119 | |
| 120 | Concerning the values of VCMAX_OPT for the PFTs 6 and 14, we simply have : [[BR]] |
| 121 | |
| 122 | {{{ |
| 123 | VCMAX_OPT__06 = 15 |
| 124 | VCMAX_OPT__14 = 15 |
| 125 | }}} |
| 126 | |
| 127 | But you would like to set 25 for the 14th PFT. For that, write in run.def : |
| 128 | |
| 129 | {{{ |
| 130 | VCMAX_OPT__14 = 25 |
| 131 | }}} |
| 132 | |
| 133 | To finish, launch your job. It's done. [[BR]] |
| 134 | This example is only an overview of the possibilities of this version. You will |
| 135 | find a user's guide here : |
| 136 | |
| 137 | UsersGuide |
| 138 | |
| 139 | |
| 140 | |
| 141 | == How to download it? == |
| 142 | |
| 143 | To be continued. For the moment please have a look at the presentation of 31012011. |