Changes between Version 100 and Version 101 of Documentation/TrunkFunctionality4

Timestamp:

2021-05-06T13:41:36+02:00 (3 years ago)

Author:

luyssaert

Comment:

--

Documentation/TrunkFunctionality4

@@ -504 +504 @@
 
 === Spin-up ===
-Describes r6614. The analytical spin-up works with ORCHIDEE trunk. To ensure growth at the onset of the analytic spin-up for all PFTs initial values are needed for the SOM pools, and that is  irrespective of whether IMPOSE_CN is y or n. The initial pools are set in stomate_io.f90, and they can be specified in the run.def by:
+Describes r7178. The analytical spin-up works with ORCHIDEE trunk. To ensure growth at the onset of the analytic spin-up for all PFTs initial values are needed for the SOM pools, and that is  irrespective of whether IMPOSE_CN is y or n. The initial pools are set in stomate_io.f90, and they can be specified in the run.def by:
 {{{
 SOM_INIT_ACTIVE = 1000
@@ -512 +512 @@
 }}} 
 The initial values of carbon for the four SOM pools are used globally. Sensitivity test have shown that the analytic spin-up is not sensitive to the actual size of the initial values. The different ecosystems will after a while settle into their own states (N limited or saturated) in spite of having the same initial state. Convergence appears to be faster if initial values are set.
+
+Whether the analytical spinup will be used or not is set in COMP/stomate.card by the parameter SPINUP_ANALYTIC. By default the SPINUP_PERIOD is calculated as the length of the time series used in cyclic_begin and cyclic_end as set in the config.card. This calculation is done in the COMP/stomate.driver
+{{{
+### Begin Code in COMP/stomate.driver                                           
+    if [ X${stomate_UserChoices_SPINUP_ANALYTIC} = Xy ] ; then                  
+       IGCM_comp_modifyDefFile nonblocker orchidee.def SPINUP_ANALYTIC y        
+                                                                                
+       # Test if CyclicBegin and CyclicEnd is set in config.card                
+       if ( [ X${config_UserChoices_CyclicBegin} = X ] || [ X${config_UserChoices_CyclicEnd} = X ] ) ; then
+           IGCM_debug_Exit "CyclicBegin and CyclicEnd must be set in config.card to run option spinup_analytic."
+       fi                                                                       
+       # Calculate and set number of years of forcing data                      
+       CycleNb=$(( ${config_UserChoices_CyclicEnd} - ${config_UserChoices_CyclicBegin} + 1 ))
+       IGCM_comp_modifyDefFile nonblocker orchidee.def SPINUP_PERIOD ${CycleNb}
+    else                                                                        
+        IGCM_comp_modifyDefFile nonblocker orchidee.def SPINUP_ANALYTIC n       
+        IGCM_comp_modifyDefFile nonblocker orchidee.def SPINUP_PERIOD -1        
+    fi                                                                                                                                       
+### End Code in COMP/stomate.driver  
+}}}
+
+The calculated value can be overwritten by setting SPINUP_PERIOD in PARAM/orchidee.def.
+ 
+In rXXXX a pre-spinup was introduced as SPINUP_ANALYTIC_FG0 and SPINUP_ANALYTIC_FG0nd. The purpose of the pre-spinup is to break the synchronicity of neighboring pixels. With FG0, all pixels will be zero years old at t=0 of the FG1 spinup. Because neighboring pixels often experience the same climate and have the same soil properties they will all mature and die within the same decade. This results in some cyclic NBP for some PFTs. FG0 is run for 200 years and within this 200 years each pixel x PFT is cut once at random (the random cutting is prescribed through a map and is therefore reproducible). This random cutting breaks the synchronicity of neighboring pixels and is thought to result quicker in a more stable steady-state (to be confimed).