wiki:DevelopmentActivities/ORCHIDEE-DOFOCO

Version 144 (modified by luyssaert, 7 years ago) (diff)

--

ORCHIDEE-CN-CAN

What to expect from this model?

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.

Known conflicts with the trunk: tot_bare_soil, VIS/NIR snow albedo

Missing functionalities compared to the trunk: DGVM, fire disturbances, and net land cover change

Missing functionalities compared to ORCHIDEE-CAN (add these and we can close the branch): wind throw, land cover change, and species change

Better functionalities than those available in the trunk, ORCHIDEE-CN or ORCHIDEE-CN-CAN: spitfire for fire disturbances and gross land cover changes.

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.

What is the future of the version?

Now that the AR6v0 is becoming stable, a robust well tested verion of ORCHIDEE can soon be committed and tagged. This gives us the opportunity to prepare for the future. The first ambition is to add CN into AR6v0 to obtain AR6v1. In parrallel we will start testing and discussing ORCHIDEE-CN-CAN to make this an acceptable trunk.

How can I contribute to this version?

Given the large number of code changes, there is no guarantee that the current version will run flawless for all set-ups and possible combinations of flags currently being used by ORCHIDEE users and developpers. Use one of the attached run.def as a starting point for your favourite set-up. Report on the outcome of your tests during the ORCHIDEE meetings.

Coupling: a first benchmark but expect many changes to come

How do I run this version?

Add instructions

Functionalities (alphabetical order)

Age classes

Age classes were introduced to better handle heterogeneity at the landscape level. The feature allows us to distinguish between different successional stages of the same PFT. Age classes are independent of the number of diameter classes. Using age classes adds a lot of details in both the biophysics and the biogeochemistry following natural disturbances, forest management and land cover change. If half of a grassland is afforested with a PFT that already exists in the pixel, previous versions of ORCHIDEE will combine this newly forest land and the existing forest in a single PFT. This will result in a low albedo, a high roughness, ... When age classes are used, the newly afforested and the existing forest will end up in separate PFTs. One will have a high albedo, the other a low, ...

Age classes were defined as separate PFTs and if wanted different age classes of the same PFT could be run with different parameters. This option has not been tested yet because it is expected to result in discontinuities when the biomass is moved from one age class to another. The number of age classes is fixed but for each PFT it can be decided whether age classes are used or not. This adds a lot of flexibility to the model. ORCHIDEE-CAN, for example, has been run with 64 PFTs, using age classes for European forest and using no age classes for all forests outside the domain of interest. Setting-up a simulation with age classes will require some thinking when setting-up the run.def. A python-script was written to create this kind of run.def. Increasing the number of PFTs has important consequences for the speed of the model and the memory use. Because a single run can contain PFTs with and PFTs without age classes, processing of the simulation output needs to account for the relationship between PFTs of the same species but a different age class.

The number of age classes is defined by the parameter NAGEC. Setting this parameter to 1 is a good start unless you have a special interest in using age classes. When NAGEC is set to more than 1, PFT_TO_MTC', AGEC_GROUP and PFT_NAME will all need to be carefully defined. See the attached run.def for a functional example. See below for some principles: NAGEC = 4 Assume we want to use four age classes for all forests. We will end-up with 37 PFTs, the 1 for bare soil, C3 grass, C4 grass, C3 crop and C4 crop and 4 times 8 for the 8 forest PFTs. Thus NVM = 37

Because we still use the 13 default MTC we can use the default maps. Let the model know how many MTCs it should find on the maps: NVMAP=13

If you want to use IMPOSE_VEG=y then only vegetation should be added to the youngest age class. ORCHIDEE will update the vegetation fractions during the simulations

SECHIBA_VEG_01=0.0769230769231
SECHIBA_VEG_02=0.0769230769231
SECHIBA_VEG_03=0.0
SECHIBA_VEG_04=0.0
SECHIBA_VEG_05=0.0
...

SECHIBA_VEGMAX_01=0.0769230769231
SECHIBA_VEGMAX_02=0.0769230769231
SECHIBA_VEGMAX_03=0.0
SECHIBA_VEGMAX_04=0.0
SECHIBA_VEGMAX_05=0.0
...

Link PFTs to MTCs

PFT_TO_MTC_01=1
PFT_TO_MTC_02=2
PFT_TO_MTC_03=2
PFT_TO_MTC_04=2
PFT_TO_MTC_05=2
...

Tell ORCHIDEE which PFTs have a successional relationship

AGEC_GROUP_01=1
AGEC_GROUP_02=2
AGEC_GROUP_03=2
AGEC_GROUP_04=2
AGEC_GROUP_05=2
...

Give all PFTs a name for clarity

PFT_NAME__01=Soilbare
PFT_NAME__02=Broadleavedevergreentropical_age01
PFT_NAME__03=Broadleavedevergreentropical_age02
PFT_NAME__04=Broadleavedevergreentropical_age03
PFT_NAME__05=Broadleavedevergreentropical_age04
...

Albedo

ORCHIDEE-CN-CAN makes use of a two stream radiative transfer scheme through the canopy. The scheme is based on Pinty et al 2006. This approach accounts not only for the leaf mass but also for the vertical and horizontal distribution of the leaf mass (=canopy structure). In ORCHIDEE-CN-CAN the same scheme is used to simulate the reflected, transmitted and absorbed light. This implies that albedo and photosynthesis are now fully consistent as well as the light reaching the forest floor (the latter is used in for example recruitment). ORCHIDEE-CN-CAN cannot revert to previous approaches for calculating albedo. The radiative transfer through the canopy is controlled by 3 parameters for each wavelength/band: single leaf scattering leaf_ssa_xxx, forward scattering leaf_psd_xxx and background reflectance bgrd_ref_xxx. At present VIS and NIR have been parameterized. Parameterization is based on running an inverse radiation scheme on the MODIS albedo product while accounting for the different land cover types. The inverted parameters are provided by the JRC as the JRC TIP product.

Allocation

ORCHIDEE-CN-CAN uses the allometric allocation as developed in OCN. In ORCHIDEE-CAN the approach was adjusted to work for more than one diameter class. Since it was developed this allocation has been used in ORCHIDEE-CN, ORCHIDEE-CNP and ORCHIDEE-MICT. In those three branches only a single diameter class was used. Except for the way the reserves and labile pools are calculated, the allocation scheme is identical between all aforementioned versions. The model is, however, very sensitive to the way the reserves and labile pools are calculated. The allocation makes use of a labile pool for which the activity is calculated based on the temperature. As such the model addresses the sink/source discussion initiated by Korner.

ORCHIDEE-CN-CAN calculates the number of individuals and uses this as a criterion to initiate a stand replacing disturbance. This approach, guided by the self-thinning relationship, avoids the need for a stand-level turnover time. ORCHIDEE-CN, ORCHIDEE-CNP and ORCHIDEE-MICT still make use of stand-level turnover.

There are no options to revert to the allocation based on resource limitation. All references and parameters for allocation based on resource limitation have been removed from the code.

MENTION K_LATOSA, CONDUCTIVITIES, SLA, RESPIRATION_COEFF, ... TAU_SAP, TAU_WOOD, ...

Background albedo

If covered by snow, the background albedo is calculated by the snow module and accounts for snow age and snow density (needs to be checked – last time snow did not account for NIR). If not covered by snow the background albedo is not simulated but prescribed by the parameters bgrd_ref_vis and bgrd_ref_nir. In deciduous forest, grasslands and croplands, the background albedo is known to be strongly affected by the phenology and senescence of the understory vegetation. ORCHIDEE-CN-CAN has two options to prescribe the background albedo:

1 - The background albedo is prescribed per PFT but is constant throughout the year. This is the option that has been used in ORCHIDEE-CAN and is the option that has been validated over Europe. Set alb_bg_modis = n.

2 - The background albedo varies with time but is constant across PFTs. This option reads background maps. Given that those maps are based on the JRC TIP product, they should be compatible with the new albedo scheme. This option, however, has not been validated yet. Set alb_bg_modis = y.

Coming soon

1 - Land cover change has been coded for age classes in ORCHIDEE-CAN. This code still needs to be merged into ORCHIDEE-CN-CAN. For the moment set land_cover_change = n and veget_update = 0Y.

2 - Following a disturbance, tree species changes and forest management change can be prescribed or read from a map in ORCHIDEE-CAN. This code still needs to be merged into ORCHIDEE-CN-CAN. For the moment set lchange_species = n, read_species_change_map = n, and read_desired_fm_map = n

Consistency checks

The code distinguishes between three options to check for mass balance problems. These options are controlled by the parameter err_act. Always use err_act = 3 when developing and testing the code. Note that in addition to checking for mass balance closure ORCHIDEE-CN-CAN will also check for the preservation of veget_max. This is useful to make sure no surface area is lost when moving biomass from one PFT to another following natural disturbances, forest management, land cover changes and when using age classes. In some parts of the code, for example, modules that deal with disturbances, it is assumed that the tallest trees are stored in the last diameter class. When the difference in diameter between diameter classes becomes very small, this assumption could be violated. Therefore, the diameter classes are sorted to enforce the assumed order and where needed the order is checked.

1 - err_act = 1 is recommended when running global long-term simulations. Under this option, mass balance closure is checked for all biogeochemical processes but only at the highest level thus stomate.f90 and stomate_lpj.f90. Although the mass balance checks are not very expensive in terms of computer time, skipping the numerous lower level checks is expected to save some time. Under this option the mass balance error is only written to the history file. No information is provided in which subroutine the problem occurred.

2 - err_act = 2 is recommended when developing and testing the model. Now the mass balance is explicitly checked in stomate.f90, stomate_lpj.f90 and all its subroutines. Under this option the mass balance error is written to the history file and if the mass balance is not closed, the warning message will indicate in which subroutine the problem likely originated.

3 - arr_act = 3 is recommended when having a problem with mass balance closure. The mass balance is explicitly checked in stomate.f90, stomate_lpj.f90 and all its subroutines. If a mass balance occurs, the model is stopped.

CWRR vs Choinel

ORCHIDEE-CN-CAN was developed and tested with CWRR. Set hydrol_cwrr to y. The Choinel code is still available. The hydrological schemes were not touched during the development of ORCHIDEE-CN-CAN.

Diameter classes

Diameter classes were introduced to better simulate the canopy structure, they are a tool to simulate heterogeneity within a single PFT. Given that the canopy is the interface between the land and the atmosphere this feature has effects well beyond forest management. Stand structure was observed to affect albedo, transpiration, photosynthesis, soil temperature, roughness length, and recruitment. Using diameter classes adds very little complexity to setting-up the simulations as well as to the output files. The complexity is mostly within the code.

The computational cost of using diameter classes is negligible and when a reasonable low number of diameter classes is used, the memory cost remains very small as the dimensions of only two variables are increased. The number of diameter classes is the same for all PFTs and is set by the parameter NCIRC. ORCHIDEE-CN, ORCHIDEE-CNP, and ORCHIDEE-MICT are all coded and used for NCIRC = 1. ORCHIDEE-CAN and ORCHIDEE-CN-CAN are coded and tested for NCIRC = 3. Until further testing, three diameter classes are considered sufficient.

Given earlier choices in ORCHIDEE, we either need to define the boundaries of each diameter class or the diameter distribution. While developing the code, we considered the second approach the most flexible. To allow maximal flexibility, each diameter class needs to be defined separately by the variable CIRC_CLASS_DIST_0000X, where X is the number of the diameter class. The smallest number presents the smallest diameter class. From literature it is known that a truncated exponential distribution is a good first guess:

CIRC_CLASS_DIST_00001=9
CIRC_CLASS_DIST_00002=3
CIRC_CLASS_DIST_00003=1 

The above declaration implies that 9/13th of the trees will always be in the smallest diameter class, 3/13th will be in the medium class and 1 tree out of 13 will be in the largest diameter class. These ratios are kept throughout the simulations and the boundaries of the diameter classes are adjusted to respect this constraint. Consequently, an even-aged stand will be simulated with three diameter classes where the diameter of the first class may be, for example, 20.3 cm, the diameter of the second class 20.4 cm and the diameter of the third class 20.5 cm. The same code and set-up allows to simulate, in the same simulation, an uneven-aged stand for the same PFT but in a different pixel with, for example, the smallest diameter 7 cm, the medium diameter 25 cm and the largest diameter 45 cm.

Forest management

70% of the global forest are managed invalidating the assumption in previous versions of ORCHIDEE that forests are long-lived natural vegetation. Forest management, inspired by ORCHIDEE-FM was implemented in ORCHIDEE-CAN. Owing to the allometric allocation scheme, the introduction of diameter classes and a canopy structure only the principles, i.e., Deleuze and Dhote and RDI based management were retained. If the forest management strategy is not specified the default value "unmanaged" (FM = 1) is used. This implies that there are no thinning or harvest. Once the stand density drops below the threshold or the tree diameter exceeds another threshold a stand replacing disturbance is applied and a new stand is prescribed in the next time step. Therefore, the biomass pools in ORCHIDEE-CN-CAN no longer depend on a prescribed longevity.

When developing and testing the model, a single forest management strategy can be applied for all pixels and PFTs. ORCHIDEE-CN-CAN distinguishes 4 different strategies:

1 – FM=1 unmanaged

2 – FM=2 high stand management: with RDI based thinnings and density/diameter based final harvest

3 – FM=3 coppice

4 – FM=4 short rotation coppice with willow or poplar

Set read_fm_map to n and specify the desired management strategy (1-4) through forest_managed_forced.

For applications that focus on forestry or require landscape heterogeneity, a PFT-specific management strategy can be read from a spatially explicit map. Thus, the same PFT in different pixels can be assigned a different management strategy. However, within a pixel a single PFT can only have one management strategy. Unless, one wants to run forest management over Europe the user will have to create his/her forest management maps first. Set read_fm_map to y and specify the location of the forest management map in COMP/stomate.card. Check the existing forest management maps for Europe for an example of how the map should be defined.

When prescribing a forest stand (independent of forest management) the Initial density nmaxtrees, and the range of the initial tree height of the seedlings needs to be specified height_init_min and height_init_max. Irrespective of the management strategy the maximum carrying capacity needs to be described. Carrying capacity was formalized through the self-thinning relationship which makes use of two parameters alpha_self_thinning and beta_self_thinning. As a fail-safe option the longevity of a stand is still defined but should only be used when all other criteria fail to kill the stand (not observed). Longevity is defined by the parameter residence_time.

The details of each of the 4 management strategies can be refined through a set of PFT-specific parameters. Note that not every management strategy makes use of all parameters. For more details see the SI of Naudts et al 2015 (last table). The different management strategies require parameter values for : first thinning height h_first, stand replacing density ntrees_dia_profit, harvest diameter max_harvest_dia, ccppice diameter coppice_diameter, rotation length src_rot_length, number of rotations src_nrots, fuelwood diameter fuelwood_diameter and the minimum and maximum alpha and beta (thus 4 parameters) specifying the RDI range alpha_rdi_upper, alpha_rdi_lower, beta_rdi_upper and beta_rdi_lower.

According to economic theory, high-stand forest are harvested when the actual growth drops below the long-term growth. This has been implemented in ORCHIDEE-CAN and ORCHIDEE-CN-CAN. This feature was found to be very sensitive to the time frame for which actual increment was calculated. This option can be by-passed by setting this period unrealistically high, for example, n_pai =1000. Persons interested in further testing/developing this feature should set this parameter (unit: years) to 5 or 10.

While developing the code some conflicts were encountered between RDI and self-thinning. As a first solution an additional threshold was introduced rdi_limit_upper. When debugging progressed this threshold was set to 0.99 (if set to 1.00 there is no correction any more). The initial problem was resolved but the initial fix has not been removed yet. For the time being set rdi_limit_upper to 0.99.

CHECK: MAX_HARVEST_DIA

Litter raking

Tree litter was collected from the forest and used in the winter stables instead of straw. In spring the litter and manure was spread on the croplands. This lateral flow of C and N between PFTS in the same pixel can be accounted for in ORCHIDEE-CN-CAN by setting use_litter_raking = y. If litter raking is to be used, the model will search for annual maps. The path of these maps needs to be specified in COMP/stomate.card. Litter raking maps were prepared for Europe. Unless liter raking is your research topic set use_litter_raking = n.

Mortality

ORCHIDEE-CN-CAN distinguished 3 types of natural mortality. The first two options are similar to those in previous version of ORCHIDEE and are set by the flag constant_mortality. If constant_mortality = y, the background mortality of a forests is calculated as a constant, prescribed fraction. In ORCHIDEE-CN-CAN, this fraction is given by residence_time (see also forest management). . If constant_mortality = y, the background mortality of a forest is a function of its net primary production (npp). If npp decreases, mortality will increase.

Both options have been developed, tested and can be used in ORCHIDEE-CN-CAN. However, because of the introduction of self-thinning mortality in ORCHIDEE-CN-CAN, constant_mortality = y soon became the default setting. In ORCHIDEE-CN-CAN, the total mortality is the maximum of the background mortality and the mortality from self-thinning. Only if self-thinning is absent or too low, background mortality will play a role. This approach implies that when constant_mortality = y is used in combination with self-thinning, background mortality will only play a role in the first years to decade before self-thinning starts. Despite its limited use, it represents an essential process: owing to background mortality, the number of individuals decreases, the remaining individuals grow faster and thus manage to reach self-thinning in a reasonable amount of time. It needs to be tested how the interplay between background mortality and self-thinning will work out when constant_mortality = n is used.

Nitrogen cycle

ORCHIDEE-CN-CAN strictly follows ORCHIDEE-CN where it concerns the implementation of the N-cycle. Following mass balance problems caused by negative N mineralization and followed by negative immobilization, the code has been slightly adjusted to ensure mass balance closure. The parameter ímpose_cn is used to control the N-cycle calculations. If set to y, C/N ratios are calculated but whenever N appears to be limiting, it is taken from the atmosphere to satisfy this need. This is the preferred setting when testing/developing the code without a proper spin-up. N-limitation will only be accounted for when setting imnpose_cn = n. With this setting the N-cycle is closed (checked when checking for mass balance closure) it will require a spin-up to produce reasonale results.

Photosynthesis

Photosynthesis is calculated as in ORCHIDEE-CAN, and ORCHIDEE-CN but the way the levels are defined has changed. The reason of this change is in the albedo and energy budget for which physical layers are required. For this reason the space between the bottom and the top of the canopy is divided into x layers. X is set by the parameter nlevels_photo. Applications with ORCHIDEE-CAN used nlevels_photo = 10. This values was retained in ORCHIDEE-CN-CAN. Contrary to ORCHIDEE-CN and previous versions of ORCHIDEE where each canopy layer contained 0.5 units of LAI, in ORCHIDEE-CN-CAN, each canopy layer will have the same depth (in m) but will contain a different amount of LAI because tree canopies are assumed spherical.

Plant water stress

MENTION 2 OPTIONS MENTION conductivities and cavitation

Recruitment

When stands grow old the tree density decreases and under certain conditions the LAI can no longer cover the ground area. When this happens productivity will start to decrease. In nature the decrease in LAI comes with an increase in the amount of light reaching the forest floor which enables seedlings to grow and to restore the LAI. This process is known as recruitment. Note that in managed forest and forest with a lot of stand replacing disturbances (for example, fire) the forest may never reach the stage where the canopy sufficiently opens up to enable recruitment.

ORCHIDEE-CN-CAN can simulate recruitment for each PFT separatly by setting recruitment_pft_xx to true or false. When using age classes it makes sense to have the same setting for all age classes of the same species. When developing and testing the code it was considered too time consuming to change the settings at the PFT level so a flag ignoring the setting for recruitment_pft_xx was introduced. If the recruitment flag is set to true, the settings of recruitment_pft_xx will be used. If the recruitment flag is set to false, the settings of recruitment_pft_xx will be ignored and the model runs without recruitment.

Recruitment has been developed, tested and validated for tropical forests. There is no reason why it shouldn't work for other forests but that needs to be confirmed. At present recruitment was introduced at the PFT level. It probably makes more sense to link it to the management strategy than to the PFT. This needs to be checked.

River routing

The river routing code was not touched during the development of ORCHIDEE-CN-CAN. This functionality has not been tested yet for ORCHIDEE-CN-CAN. Unless rivers are your main interest, set river_routing to n.

Single layer vs multi layer energy budget

There are still some issues with the multi-layer energy budget, and it is currently only possible to run for one PFT. Thus, we suggest you use the single layer energy budget. This can, however, be done by two different methods that gives the exact same results:

A: use the energy scheme as found in the original enerbil.f90

B: use the multi-layer energy scheme for a single canopy layer. This collapses the multi-layer energy scheme to the original enerbil code, but if you wish to take hydraulic water stress with feedback on stomatal conductance into account in your simulation, you need to choose this method.

Several flags exist to control these choices. For simplicity, a flag has been made to automatically control several of the flags related to the multi-layering, called multi_layer_control. Multi_layer_control has 4 possibilities

1 – single layer, using the multi layer energy scheme (i.e. choice B above)

2 – multi-layer energy budget

3 – user specific as set in the run.def

4 – single layer, using the original enerbil scheme (i.e. choice A above)

The default setting of multi_layer_control in ORHIDEE-CN-CAN is 1. This is well tested and considered save to use. More details of the flags controlling the multi-layer can be found below and within the model code.

The flags controlled by the multi_layer_control are:

ok_hydrol_arch: Flag that activates the hydraulic architecture routine (true/false). The trunk version of ORCHIDEE (false) uses soil water as a proxy for water stress and applies the stress to Vcmax. When set to true the hydraulic architecture of the vegetation is accounted for to calculate the amount of water that can be transported through the plant given the soil and leaf potential and the conductivities of the roots, wood and leaves. Water supply through the plant is compared against the atmospheric demand for water. If the supply is smaller then the demand, the plant experiences water stress and the stomata will be closed (water stress is now on gs rather than Vcmax). Note that whether stomatal regulation is used or not is controled by a separate flag: ok_gs_feedback. ok_gs_feedback: Flag that activates water stress on stomata (true/false). This flag is for debugging only! It allows developers to calculate GPP without any water stress. If the model is used in production mode and ok_hydrol_arch is true this flag should be true as well.

ok_mleb: Flag that activates the multilayer energy budget (true/false). The model uses 10 (default) canopy layers to calculate the albedo, transmittance, absorbance and GPP. These canopy layers can be combined with 10 (default) layers below and 9 layers above the canopy to calculate the energy budget (ok_mleb=y). If set to no, this flag will make the model use 10 layers for the canopy albedo, transmittance, absorbance and GPP and just a single layer for the energy budget. Be aware that if you wish to run with hydraulic architechture ok_mleb needs to be se to true as well. Furthermore, if you wish to run with the original energy scheme (enerbil), set the layers for mleb to 1.

ok_impose_can_structure: This flag is for debugging only! It allows developers to use a prescribed canopy structure rather then the structure calculate by ORCHIDEE. The flag activates the sections of code which directly link the energy budget scheme to the the size and LAI profile of the canopy for the respective PFT and age class that is calculated in stomate, for the albedo. If set to TRUE and the multi-layer budget is activated the model takes LAI profile information and canopy level heights from the run.def. If set to FALSE, and the multi-layer energy budget is used the profile information and canopy levels heights comes from the PGap-based processes for calculation of stand profile information in stomate.

ok_mleb_history_file: Flag that controls the writing of an output file with the multi-layer energy simulations (true/false). Note that this is a large file and writing slows down the code.

The multi_layer_control set these flags in the following manner:

1 – single layer, using the multi layer energy scheme

       ok_hydrol_arch = .TRUE.;  
       ok_gs_feedback = .TRUE.; 
       ok_mleb = .TRUE.; 
       ok_impose_can_structure = .TRUE.; 
       ok_mleb_history_file = .FALSE.

2 – multi-layer energy budget

       ok_hydrol_arch = .TRUE.; 
       ok_gs_feedback = .TRUE.; 
       ok_mleb = .TRUE.; 
       ok_impose_can_structure = .FALSE.; 
       ok_mleb_history_file = .FALSE.

3 – user specific as set in the run.def

       All read from the run.def

4 – single layer, using the original enerbil scheme

       ok_hydrol_arch = .FALSE.; 
       ok_gs_feedback = .FALSE.; 
       ok_mleb = .FALSE.; 
       ok_impose_can_structure = .FALSE.; 
       ok_mleb_history_file = .FALSE.

Specific leaf area

Similar to ORCHIDEE-CN, ORCHIDEE-CN-CAN users can choose to use a constant specific leaf area (SLA) or a dynamic (SLA) by setting the flag dyn_sla. SLA is a fundamental parameter in the allocation scheme and it is well established that SLA is dynamic in nature especially during leaf onset. The current implementation of dynamic SLA is basic and there is room to enhance consistency in the calculations, for example, by recalculation the allocation factors KF and LF as a function of SLA.

Stomate

ORCHIDEE-CN-CAN strengthen the links between sechiba and stomate. As in previous versions, stomate makes use of variables calculated in sechiba but in ORCHIDEE-CAN and ORCHIDEE-CN-CAN, sechiba requires information from stomate to work properly. For the moment set stomate_ok_stomate to y (_AUTOBLOCKER_). For the future it seems possible to prescribe LAI and assume a canopy structure but this code still needs to be restored and tested. For the time being set lai_map = n.

Attachments (8)