Changes between Version 1 and Version 2 of DevelopmentActivities/Bugs


Ignore:
Timestamp:
2015-12-02T14:29:46+01:00 (9 years ago)
Author:
ajornet
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • DevelopmentActivities/Bugs

    v1 v2  
    44 
    55== List == 
     6 
     7=== PFT maps and Analytic spinup with DGVM === 
     8 
     9You have a list in pft_parameters: 
     10 
     11{{{ 
     12      !! 5.1 Read the name of the PFTs given by the user 
     13      ! 
     14      !Config Key   = PFT_NAME 
     15      !Config Desc  = Name of a PFT 
     16      !Config if    = OK_SECHIBA or OK_STOMATE 
     17      !Config Def   = bare ground, tropical broad-leaved evergreen, tropical broad-leaved raingreen, 
     18      !Config         temperate needleleaf evergreen, temperate broad-leaved evergreen temperate broad-leaved summergreen, 
     19      !Config         boreal needleleaf evergreen, boreal broad-leaved summergreen, boreal needleleaf summergreen, 
     20      !Config         C3 grass, C4 grass, C3 agriculture, C4 agriculture 
     21      !Config Help  = the user can name the new PFTs he/she introducing for new species 
     22      !Config Units = [-] 
     23      CALL getin_p('PFT_NAME',pft_name) 
     24}}} 
     25 
     26This is independent from Chao's problem. I'm looking at DGVM without SPITFIRE. In dynamic mode, we have first crops but natural PFTs appear later: grasses and after a few years trees. At least that's how it behaves with the TRUNK version. 
     27 
     28=== Spitfire === 
     29 
     30* There are regative values at fuel_XXhr variables 
     31* Multiple floating point exceptions at reat_of_spread 
     32 
     33=== VSD merge === 
     34 
     35How to deal with already designed MICT soil layers ? 
     36 
     37 
     38Hi Shushi, 
     39 
     40I made a mystake last Monday because the new vertical discretization had not yet been integrated in Albert's personal branch. Albert is now working on it and we have a few questions. 
     41 
     42In Albert's branch, we have two possible different sets of values for soil_capa and soil_cond based on the keyword SOIL_LAYERS_DISCRE_METHOD (see constantes_soil.f90 and get_discretization_constants in thermosoil.f90). 
     43 
     44This gives access to two different vertical discretization shemes (see thermosoil_levels). I copied all this relevant code below. 
     45 
     46 
     471. Do we agree that we completely let down these two discretization schemes to get the new one (see vertical_soil_init)? 
     48 
     492. I have the impression that soil_capa and soil_cond may intervene elsewhere, do we still keep the two different sets of values? 
     50 
     51=== New Drivers === 
     52 
     53Test performance