Changes between Version 2 and Version 3 of Documentation/UserGuide/ImposeVegetation


Ignore:
Timestamp:
2013-09-13T14:06:23+02:00 (11 years ago)
Author:
luyssaert
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • Documentation/UserGuide/ImposeVegetation

    v2 v3  
    11= How to prescribe (or impose in ORCHIDEE terminology) the vegetation in a pixel? = 
    22 
    3 Many new ORCHIDEE users will impose their preferred vegetation to a single pixel. This has the advantage that simulations go faster, output files are smaller, data-model comparison is more straightforward and it is easier to understand the effect of specific settings and parameters. 
     3Many new ORCHIDEE users will impose their preferred vegetation to a single pixel. This has the advantage that simulations go faster, output files are smaller, data-model comparison is more straightforward and it is easier to understand the effect of specific settings and parameters. To do so you will to make changes to ../config/ORCHIDEE_OL/COMP/sechiba.card and ../config/ORCHIDEE_OL/PARAM/run.def  
    44 
    5  
    6 First, state that you no longer want to impose the vegetation 
     5First, state that you want to impose the vegetation 
    76{{{ 
    87# IMPOSE_VEG=y/n 
    9 IMPOSE_VEG=n 
     8IMPOSE_VEG=y 
    109}}} 
    1110 
    12 Use the same land cover map for all the years in your simulation. Thus don't make use of land cover change (see another how to for the settings to account for land cover change) 
     11Make sure you don't overwrite your own settings in the next time step, hence, switch of land cover change 
    1312{{{ 
    1413# Set LAND_COVER_CHANGE=y if VEGET_UPDATE > 0 
     
    1716 
    1817 
    19 Because land cover change is not accounted for, the land cover map should never be updated 
     18Obviuosly, you don't want to update the land cover map because you're not using one 
    2019{{{ 
    2120# VEGET_UPDATE=0Y no change in PFTmap. PFTmap should be set only in InitialStateFiles/List.  
     
    2524}}} 
    2625 
    27 The land cover map is now a map that needs to be read at the start of the simulation. It represents part of the initial state of the model 
     26The land cover map should not be specified in Initial state list of the model 
    2827{{{ 
    2928[InitialStateFiles] 
     
    3130            (${R_INIT}/SRF/${config_UserChoices_TagName}/soils_param.nc, .), \ 
    3231            (${R_INIT}/SRF/${config_UserChoices_TagName}/cartepente2d_15min.nc, .), \ 
    33             (${R_INIT}/SRF/${config_UserChoices_TagName}/floodplains.nc, .), \ 
    34             (${R_INIT}/SRF/${config_UserChoices_TagName}/carteveg5km.nc, carteveg5km.nc) 
     32            (${R_INIT}/SRF/${config_UserChoices_TagName}/floodplains.nc, .) 
    3533}}} 
    3634 
     
    4139}}} 
    4240 
    43 Although the sechiba.card has priority over the run.def a little consistency doesn't hurt so make sure that the run.def does NOT contain impose_veg=y, values for SECHIBA_VEG and values for SECHIBA_VEGMAX 
     41 
     42Because their is no initial state for the model it needs to be specified in the run.def.  
     43 
     44For consistency reasons add to the rund.def 
     45{{{ 
     46impose_veg=y 
     47}}} 
     48 
     49It is essential to specify  
     50{{{ 
     51SECHIBA_VEG__01 = x1 
     52... 
     53SECHIBA_VEG__nvm = xnvm 
     54}}} 
     55 
     56Where the sum of x1 to xnvm should equal 1 
     57 
     58 
     59Although some branches no longer make use of it, it is better to specify SECHIBA_VEGMAX as well. Just copy the values of SECHIBA_VEG to avoid problems 
     60