=Current Bugs=

List of bugs that need to be fixed. They are order by priority from the top to the bottom.

== List ==

=== PFT maps and Analytic spinup with DGVM ===

You have a list in pft_parameters:

{{{
      !! 5.1 Read the name of the PFTs given by the user
      !
      !Config Key   = PFT_NAME
      !Config Desc  = Name of a PFT
      !Config if    = OK_SECHIBA or OK_STOMATE
      !Config Def   = bare ground, tropical broad-leaved evergreen, tropical broad-leaved raingreen,
      !Config         temperate needleleaf evergreen, temperate broad-leaved evergreen temperate broad-leaved summergreen,
      !Config         boreal needleleaf evergreen, boreal broad-leaved summergreen, boreal needleleaf summergreen,
      !Config         C3 grass, C4 grass, C3 agriculture, C4 agriculture
      !Config Help  = the user can name the new PFTs he/she introducing for new species
      !Config Units = [-]
      CALL getin_p('PFT_NAME',pft_name)
}}}

This 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.

=== Spitfire ===

* There are regative values at fuel_XXhr variables
* Multiple floating point exceptions at reat_of_spread

=== VSD merge ===

How to deal with already designed MICT soil layers ?


Hi Shushi,

I 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.

In 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).

This gives access to two different vertical discretization shemes (see thermosoil_levels). I copied all this relevant code below.


1. Do we agree that we completely let down these two discretization schemes to get the new one (see vertical_soil_init)?

2. I have the impression that soil_capa and soil_cond may intervene elsewhere, do we still keep the two different sets of values?

=== New Drivers ===

Test performance