| 4 | | ORCHIDEE-CN-CAN is a combination of three code bases: the trunk as it is in 2019, the ORCHIDEE-CN branch in 2016 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 has not yet committed (for example, the DGVM). Nevertheless, this light version is believed to contain all functionality that affects the parameterization of the core of the model. Consider the model as two parts: 1) core processes that effect fluxes and pools on the per square meter level, and 2) perirpheric processes that involve everything else. In this picture, the functionality that is not yet included depends on core processes like vegetation growth, soil hydrology or the energy budget, but it does not affect these processes at the pixel level. |
| | 4 | ORCHIDEE-CN-CAN is a combination of three code bases: the trunk as it is in 2020, the ORCHIDEE-CN branch in 2016 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 has not yet committed (for example, the DGVM). Nevertheless, this light version is believed to contain all functionality that affects the parameterization of the core of the model. Consider the model as two parts: 1) core processes that affect fluxes and pools on the per square meter level, and 2) perirpheric processes that involve everything else. In this picture, the functionality that is not yet included depends on core processes like vegetation growth, soil hydrology or the energy budget, but it does not affect these processes at the pixel level. |
| 13 | | Now that the AR6v1 is stable, a robust well tested version of ORCHIDEE has been tagged. This gives the ORCHIDEE-team the opportunity to prepare for the future by making a series of far reaching changes to the code. The first ambition is to add CN into AR6v0 to obtain Tag 3.0 before the end of 2019. In parallel, ORCHIDEE-CN-CAN has been merged with the TRUNK during the year of 2019 to prepare for Tag 4.0. We will continue testing and discussing Tag 4.0 before making this the trunk for both coupled and off-line simulations. The basis of Tag 4.0 is the current ORCHIDEE trunk (the version to become Tag 3.0) into which CAN functionality is merged. At this stage key functionality from other branches may be merged as well (to be discussed in tandem with the fair use policy). In addition to the recent improvements to the trunk, the new trunk (Tag 4.0) should have an increased functionality (see below), increased internal consistency (see below, for example albedo and photosynthesis) and some long awaited fixes (see below, for example tot_bare_soil). |
| | 13 | Now that the AR6v1 is stable, a robust well tested version of ORCHIDEE has been tagged. This gives the ORCHIDEE-team the opportunity to prepare for the future by making a series of far reaching changes to the code. The first ambition is to add CN into AR6v0 to obtain Tag 3.0 very early in 2020. In parallel, ORCHIDEE-CN-CAN has been merged with the TRUNK during the year of 2019 to prepare for Tag 4.0. We will continue testing and discussing Tag 4.0 before making this the trunk for both coupled and off-line simulations. The basis of Tag 4.0 is the current ORCHIDEE trunk (the version to become Tag 3.0) into which CAN functionality is merged. At this stage key functionality from other branches may be merged as well (to be discussed in tandem with the fair use policy). In addition to the recent improvements to the trunk, the new trunk (Tag 4.0) should have an increased functionality (see below), increased internal consistency (see below, for example albedo and photosynthesis) and some long awaited fixes (see below, for example mass balance closure). |
| 22 | | The instructions to download and extract ORCHIDEE-CN-CAN are found on the wiki (see https://forge.ipsl.jussieu.fr/orchidee/wiki/Documentation/UserGuide/ORCHIDEEDOFOCOInstall). When you check-out the model, you also check-out OCRHIDEE_OL, where OOL_SEC_STO_FG1trans, OOL_SEC_STO_FG2 and SPINUP_ANALYTIC_FG1 have been updated to contain the configurations needed to run ORCHIDEE-CN-CAN. The configurations are based on the ORCHIDEE_OL from the trunk as of December 2018. In ORCHIDEE_OL there is a MAKE_RUN_DEF folder. This folder contains the parameter values and a script that will make all run.defs CN-CAN users have requested this far (i.e. 13, 15, 28 and 37 PFTs both for the FG2 and ENSEMBLE configuration). If you would like to use another run.def let us know and we can help you to adjust the script. |
| 23 | | |
| 24 | | When running the model, the default setting should be XIOS, thus compile the model with gmake. |
| 25 | | |
| 26 | | If you chose to use your own configurations to run ORHICDEE-CN-CAN, be aware that new output files have been added to ORCHIDEE-CN-CAN, and this has to be specified in the cards and drivers. |
| 27 | | |
| 28 | | Below is given an example for stomate_history_4dim. |
| | 21 | The instructions to download and extract ORCHIDEE-CN-CAN are found on the wiki (see https://forge.ipsl.jussieu.fr/orchidee/wiki/Documentation/UserGuide/ORCHIDEEDOFOCOInstall). When you check-out the model, you also check-out OCRHIDEE_OL, where OOL_SEC_STO_FG1trans, OOL_SEC_STO_FG2 and SPINUP_ANALYTIC_FG1 have been updated to contain the configurations needed to run ORCHIDEE-CN-CAN. The configurations are based on the ORCHIDEE_OL from the trunk as of December 2018. OOL_SEC_STO_FG4 and OOL_SEC_STO_FG5 are configurations in which classic CAN functionality is used: species, age classes, forest management and litter raking. In ORCHIDEE_OL there is a MAKE_RUN_DEF folder. This folder contains the parameter values and a script that will make all run.defs CN-CAN users have requested this far (i.e. 3, 13, 15, 28 and 37 PFTs both for the FG2 and ENSEMBLE configuration). If you would like to use another run.def let us know and we can help you to adjust the script. |
| | 22 | |
| | 23 | When running the model, the default setting should be XIOS, thus compile the model with gmake. If you chose to use your own configurations to run ORHICDEE-CN-CAN, be aware that new output files have been added to ORCHIDEE-CN-CAN, and this has to be specified in the cards and drivers. Below is given an example for stomate_history_4dim. |
