Changes between Version 2 and Version 3 of DevelopmentActivities/ORCHIDEE-MICT-IMBALANCE-P/Evaluation

Timestamp:

2015-08-25T10:22:39+02:00 (9 years ago)

Author:

maignan

Comment:

--

DevelopmentActivities/ORCHIDEE-MICT-IMBALANCE-P/Evaluation

@@ -74 +74 @@
 == Notes from F. Maignan ==
 
-=== 2015/08/21 ===
-I've started a 2 degree V6 evaluation here:
+I've started a 2 degree V6 evaluation at LSCE here:[[BR]]
 /home/surface3/maignan/ORCHIDEE/TESTS/test_MICT_V6/modipsl/modeles/ORCHIDEE/modipsl/config/ORCHIDEE_OL/OOL_SEC_STO_V6[[BR]]
 
@@ -81 +80 @@
 
 
-* Bugs
- - stomate_Cforcing_name and stomate_forcing_name
+=== '''Bugs''' ===
+* '''stomate_permafrost_carbon / snow_interpol / ! 5. inter- or extrapolate''' (2015/08/24)[[BR]]
+{{{
+IF ( dzio(ip,iv) .GT. 0. ) THEN
+}}}
+should be replaced with:
+{{{
+IF ( dzio(ip,iv) .GT. min_stomate ) THEN
+}}}
+dzio(ip,iv) can be very small and there is a subsequent division per zero and orchidee crashes.
+
+* '''stomate_Cforcing_name and stomate_forcing_name''' (2015/08/21)
 I've found a problem with the variable Cforcing_name, which is declared both as a global save variable of the stomate module and as a save variable of the stomate_main procedure. It is read in stomate_initialize using a getin_p but indeed the value is not correctly transmitted to the stomate_main procedure. There is also a stomate_Cforcing_name in constantes_var.
 
@@ -91 +100 @@
 I don't know where this weird code originates from, I hope it's OK with forcesoil and teststomate, I'll check later.
 
-* To be corrected
+=== '''To be corrected''' ===
+* 2015/08/24
+ - LIGHTNING_FILE should not be read if FIRE_DISABLE=y
+* 2015/08/21
  - GRAZING_MAP should not be read if grassland management is not activated.
  - If OK_EXPLICITSNOW is FALSE then snowdz is not initialized but used anyway (this is probably the case of other variables, to be checked).