Changes between Version 4 and Version 5 of Documentation/UserGuide/NewForcingVerif


Ignore:
Timestamp:
2020-02-28T11:43:34+01:00 (4 years ago)
Author:
cottle
Comment:

--

Legend:

Unmodified
Added
Removed
Modified

  • Documentation/UserGuide/NewForcingVerif

    v4 v5  
    11 
    22= '''Verification of new meteorological forcing files''' = 
     3Update C. Ottle 02/28/2020 
    34 
    4  
    5 Several meteorological forcing emerge in the land surface modelling community and are using by the ORCHIDEE team to run the model in offline mode. To this end, the forcing datasets need to be adapted beforehand for their reading and the inter/extrapolation by the driver of ORCHIDEE. The purpose of this protocole is to build a systematic verification whenever a new forcing is going to be used for offline simulations. 
     5Several meteorological forcings are available in the land surface modelling community and are used by the ORCHIDEE team to run the model standalone (not coupled with LMDZ). To this end, the forcing datasets need to be adapted beforehand for their reading and the inter/extrapolation by the driver of ORCHIDEE. The purpose of this protocole is to build a systematic verification when a new forcing is going to be used. 
    66 
    77 
    88== 1. '''NetCDF file construction rules''' == 
    99 
    10 The ORCHIDEE driver requires specific informations and conventions in the structure of the NetCDF files of the new forcing to be able to read them. Therefore, it is required to format the raw files following all the informations described at this page: https://forge.ipsl.jussieu.fr/orchidee/wiki/Documentation/Forcings 
     10The ORCHIDEE driver requires specific informations and conventions in the structure of the NetCDF files of the atmospheric forcing to be able to read them. Therefore, it is required to format the raw files following all the informations described at this page: https://forge.ipsl.jussieu.fr/orchidee/wiki/Documentation/Forcings 
    1111 
    1212* you can find here examples of scripts which have been used to format files of several forcing: 
    1313 * Jinfeng Chang's scripts used for GSWP3 v0 forcing formatting on obelix (LSCE): /home/surface7/jchang/GSWP3_3hr/. [[BR]] 
    14  Warning: this script does not include these nco commands which are required to shift one step backward all the GSWP3 variables. Once you applied Jinfeng's script, you have to apply nco commands, for example (by Vladislav Bastrikov and Nicolas Vuichard): 
     14 Warning: this script does not include the nco commands which are required to shift one step backward all the GSWP3 variables. Once you applied Jinfeng's script, you have to apply nco commands, for example (by Vladislav Bastrikov and Nicolas Vuichard): 
    1515{{{ 
    1616ncks -a -d tstep,1, GSWP3_XXX_2002.nc temporary_2002.nc 
    … …  
    2222== 2. '''Verification of the good reading and inter/extrapolation by the driver''' == 
    2323 
    24 To know if the driver read and inter/extrapolated well the atmospheric forcing files, the best way is to perform one-year offline simulation with ORCHIDEE forced by this new forcing 
     24To know if the driver read and inter/extrapolate well the atmospheric forcing files, the best way is to perform one-year offline simulation with ORCHIDEE forced by this new forcing 
    2525  * the meteorological variables (Tair, Qair, Psurf, Rainf,Snowf, SWdown and LWdown) have to be written in high-frequency (30min) outputs 
    2626 
    2727The 30-min outputs are compared with the original forcing file 
    28   * for a given variable (Swdown is a special case, see below), the diurnal cycle should match between the ORCHIDEE 30-min output file and the forcing file 
    29    * example of an IDL script (from Fabienne Maignan on obelix at LSCE) which plots an average seasonal cycle at 30min time step (the script has to be adapted before using because it used watchout files that have been removed a long time ago): [/home/users/maignan/IDL/ORCHIDEE/FORCAGES/CRUNCEP/TestForcagesCRUNCEP.pro] 
     28  * for a given variable (SWdown is a special case, see below), the diurnal cycle should match between the ORCHIDEE 30-min output file and the forcing file 
     29   * example of an IDL script (from Fabienne Maignan on obelix at LSCE) which plots an average seasonal cycle at 30min time step (the script has to be adapted before using it because it uses watchout files that have been removed a long time ago): [/home/users/maignan/IDL/ORCHIDEE/FORCAGES/CRUNCEP/TestForcagesCRUNCEP.pro] 
    3030 
    31   * '''for Swdown''': as the driver also uses the zenith angle when it interpolates the time of Swdown, we need to check its diurnal cycle over a grid-cell at Greenwich, in a 24h-day of June for example, to ensure that the SWdown should peaks at noon exactly (as recommended at the end of this document: https://forge.ipsl.jussieu.fr/orchidee/attachment/wiki/Documentation/Forcings/Description_Forcing_Files.pdf) 
     31  * '''for SWdown''': as the driver also uses the zenith angle when it interpolates the time of SWdown, we need to check its diurnal cycle over a grid-cell at Greenwich, in a 24h-day of June for example, to ensure that SWdown peaks at noon exactly (as recommended at the end of this document: https://forge.ipsl.jussieu.fr/orchidee/attachment/wiki/Documentation/Forcings/Description_Forcing_Files.pdf) 
    3232 
    3333