Changes between Version 112 and Version 113 of DevelopmentActivities/ORCHIDEE-DOFOCO


Ignore:
Timestamp:
2017-06-01T15:04:55+02:00 (8 years ago)
Author:
luyssaert
Comment:

--

Legend:

Unmodified
Added
Removed
Modified

  • DevelopmentActivities/ORCHIDEE-DOFOCO

    v112 v113  
    11= ORCHIDEE-CN-CAN = 
    22 
    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.  
     3== What to expect from this model? == 
     4ORCHIDEE-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.   
    55 
    6 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 (see below).  
     6Known conflicts with the trunk: tot_bare_soil, VIS/NIR snow albedo 
     7Missing functionalities compared to the trunk: DGVM, fire disturbances, and net land cover change 
     8Missing functionalities compared to ORCHIDEE-CAN (add these and we can close the branch): wind throw, land cover change, and species change 
     9Better functionalities than those available in the trunk, ORCHIDEE-CN or ORCHIDEE-CN-CAN: spitfire for fire disturbanmces and gross land cover changes. 
     10  
    711 
    8 ==What is the future of the version?==    
    9    
    10 ==How can I contribute to this version?== 
     12== What is the future of the version? ==    
     13Now 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.   
    1114 
    12 ==How do I run this version?== 
     15    
     16== How can I contribute to this version? == 
     17Given 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. 
     18  
    1319 
    14 ==Some explanaitions about the (new) parameters== 
     20== How do I run this version? == 
     21Add instructions 
    1522 
     23== Some explanations about the (new) parameters == 
     24=== Allocation === 
     25=== Age classes === 
     26=== Diameter classes === 
     27=== CWRR vs Choinell === 
     28=== Albedo === 
     29=== Background albedo === 
     30=== Single layer vs multi layer energy budget === 
     31=== Plant water stress === 
     32=== Dynamic SLA === 
     33=== Forest management === 
     34=== Consistency checks === 
     35=== Nitrogen cycle === 
     36=== Recruitment === 
     37