| 3 | | == What to expect from this model? == |
| 4 | | ORCHIDEE-CN-CAN is based on the latest version of the trunk, the latest version of the ORCHIDEE-CN branch and the key functionality of ORCHIDEE-CAN (aka ORCHIDEE-DOFOCO on the svn server). The committed version can be considered a light version of ORCHIDEE because some of the available functionality was not yet commited (for example, the DGVM). Nevertheless, this light version is believed to contain all functionality that affects the parameterization of the model. The functionality that is not yet included depends on vegetation growth, soil hydrology or the energy budget but does not affect these processes at the pixel level. |
| 5 | | |
| 6 | | Known conflicts with the trunk: tot_bare_soil, VIS/NIR snow albedo |
| 7 | | |
| 8 | | Missing functionalities compared to the trunk: DGVM, fire disturbances, and net land cover change |
| 9 | | |
| 10 | | Missing functionalities compared to ORCHIDEE-CAN (add these and we can close the branch): wind throw, land cover change, and species change |
| 11 | | |
| 12 | | Better functionalities than those available in the trunk, ORCHIDEE-CN or ORCHIDEE-CN-CAN: spitfire for fire disturbances and gross land cover changes. |
| 13 | | |
| 14 | | Coupling: Trunk has been extensively tested, ORCHIDEE-CN? ORCHIDEE-CAN has been used nudged and zoomed. Several key parameters have changed: albedo, roughness is now dynamic, more landscape heterogeneity when using age classes. |
| | 3 | ORCHIDEE-CN-CAN is based on the latest version of the trunk, the latest version of the ORCHIDEE-CN branch and some key functionality of ORCHIDEE-CAN (aka ORCHIDEE-DOFOCO on the svn server). The committed version can be considered a light version of ORCHIDEE because some of the available functionality was not yet committed (for example, the DGVM). Nevertheless, this light version is believed to contain all functionality that affects the parameterization of the model. The functionality that is not yet included depends on vegetation growth, soil hydrology or the energy budget but does not affect these processes at the pixel level. |
| | 4 | |
| | 5 | 1 - The available functionality is described in more detail below. |
| | 6 | |
| | 7 | 2 - Known conflicts with the trunk: tot_bare_soil, VIS/NIR snow albedo |
| | 8 | |
| | 9 | 3 - Missing functionalities compared to the trunk: DGVM, fire disturbances, and net land cover change |
| | 10 | |
| | 11 | 4 - Missing functionalities compared to ORCHIDEE-CAN (add these and we can close the branch): wind throw, land cover change, and species change |
| | 12 | |
| | 13 | 5 - Better functionalities than those available in the trunk, ORCHIDEE-CN or ORCHIDEE-CN-CAN: spitfire for fire disturbances and gross land cover changes. |
| | 14 | |
| | 15 | 6 - Coupling: the latest trunk has been extensively tested as part of the AR6 efforts. Has ORCHIDEE-CN been tested in the coupling? LMDZ coupled with ORCHIDEE-CAN has been used only with nudging and zoomed over Europe. Given that several key parameters for the coupling have changed: albedo, roughness is now dynamic, more landscape heterogeneity when using age classes, transpiration, … it is expected that lots of testing will be required to come to a satisfying result with LMDzOR-CN-CAN. |
| | 16 | |
