Opened 4 years ago

Closed 4 years ago

#532 closed enhancement (fixed)

Check the use of cn_leaf_min_season

Reported by: luyssaert Owned by: somebody
Priority: minor Milestone: IPSLCM6.v2
Component: Biogeochemical processes Version:
Keywords: Cc:


In stomate_growth_fun_all and stomate_phenology cn_leaf_min_season was used. This variable is undefined when there are no leaves. This means that we cannot simulate allocation before budbreak. The use of a labile pool in combination with gtemp foresees, however, the possibility to carbon is moved around before budbreak.

As a solution cn_leaf_min_season was replaced by cn_leaf_min_2D. Is this an acceptable solution? What is the conceptual difference between both variables? If this solution is acceptable cn_leaf_min_2d will need to be passed through age_clean and LCC.

The change that was made in stomate_growth_fun_all looks like:

! Prescribe the C:N ratio
! the original code propose cn_leaf_min_season which is calculated in stomate
! for deciduous trees cn_leaf_min_season = zero when there are no leaves but
! there could still be allocation due to the labile pool. Try using a different
! default value

There is a similar change in phenology!

Change History (2)

comment:1 Changed 4 years ago by luyssaert

In r5955 cn_leaf_min_season is used as in the trunk. The zeros mentioned abpove were caused because cn_leaf_min_season was calculated for the day that plant_status = ibudbreak. ibudbreak is set to icanopy in stomate_season. The calculation of cn_leaf_min_season should therefore be done before the call to stomate_season (in stomate.f90). Plant_status is not used in the trunk and the calculation of cn_leaf_min_season was done right after the call to stomate_season.

comment:2 Changed 4 years ago by luyssaert

  • Resolution set to fixed
  • Status changed from new to closed

In r5956 cn_leaf_min_season is calculated in the same way as in the trunk. This calculation was moved from stomate to stomate_season as that seems better in line with the model architecture.

Note: See TracTickets for help on using tickets.