Changes between Version 123 and Version 124 of Documentation/Forcings


Ignore:
Timestamp:
02/23/21 10:38:14 (4 months ago)
Author:
xnwang
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • Documentation/Forcings

    v123 v124  
    9696  This driver is expected to be more flexible and to deal with any temporal structure of the forcing datasets, provided the required attributes are inserted in the forcing files. This document [attachment:Description_Forcing_Files.pdf] provides details of how forcing files need to be prepared. It addresses in particular the issues one may face when the fluxes are averaged and scalar variables are instantaneous. The driver needs to take this into account,otherwise the diurnal cycle can be misplaced. Some data providers have different conventions for representing averaged fluxes, and such information is important to know.   
    9797 
    98 * '''cell_methods time attribute''': you need to add a time attribute to each variable, e.g. "time: instantaneous" our "time: mean(end)", further details in [attachment:Description_Forcing_Files.pdf].   
     98* '''cell_methods time attribute''': you need to add a time attribute to each variable, e.g. "time: instantaneous" our "time: mean(end)", further details in [attachment:Description_Forcing_Files.pdf]. The new driver can work with forcing files of various cell methods, while the old driver works with specific forcing data (CRU). 
     99  
    99100 
    100101* '''SPRED_PREC''': In the driver files precipitation is the accumulated value over the time step of the driver file (e.g. 6 hours). In ORCHIDEE it needs to be decided whether over which time period (in seconds) this precip will come down. Short periods make rain storms, long periods make drizzel. In the new driver, we have '''SPRED_PREC_SEC''' in PARAM/run.def with a relative small value, ie., 3600 (ie., 1hour) by default. 
    101102 
    102 The structure of the new driver code is quite different from the older driver. While the older driver has the main code dim2_driver.f90 by calling readdim2.f90, the main code of new driver is  orchideedriver.f90 by calling globgrd.f90, forcing_tools.f90, forcingdaily_tools etc.  
     103* '''restart file''': The new driver does not need the restart file in the orchideedriver.card, while the old driver does have restart file in the orchidee_ol.card.  
     104 
     105The structure and the organisation of the new driver code is quite different from the older driver. While the older driver has the main code dim2_driver.f90 by calling readdim2.f90, the main code of new driver is  orchideedriver.f90 by calling globgrd.f90, forcing_tools.f90, forcingdaily_tools etc.  
    103106 
    104107* The organisation and the structure of orchideedriver.f90 are improved compared to dim2_driver.f90, with more comments in the codes. 
     
    124127* fortran code: significant modification to src_driver/forcing_tools.f90, slight change to src_driver/orchideedriver.f90 
    125128* libIGCM : libIGCM/libIGCM_config/libIGCM_config.ksh 
    126 * configuration files: COMP/orchideedriver.driver , PARAM/run.def , PARAM/orchidee.def : routing=n (in the tests by using forcing files of coarse resolution) 
     129* configuration files: COMP/orchideedriver.driver ( mainly for spinup analysitic and fg1trans) , PARAM/run.def ( mainly for spinup analysitic and fg1trans), PARAM/orchidee.def : routing=n (in the tests by using forcing files of coarse resolution) 
    127130* A new script AddYears : to prepare for the forcing files, which is to be integrated to the modele/utils. (This script was modified and generalized based a script of Jan). 
    128131 
     
    133136        Suppose that we have forcing files over 1901-1910, we need forcing files for 1900 and 1911 when using the new driver. The script AddYears is to prepare for such forcing files. 
    134137        * If we can put the new forcing files into the forcing repository: the users do not need run this script, or modify the data path in .card. Running a simulation with new driver will be the same as the old one, since the good configuration files .card should be in the experiment folder. 
    135         * If the additional forcing files are not in the IGCM repository, the users need to: a) run the script AddYears firstly, b) then modify the forcing path in the orchideedriver.card by using the right path to the forcing files before launching simulation. 
     138        * If the additional forcing files are not in the IGCM repository, the users need to: a) run the script AddYears firstly, b) then modify the forcing path in the orchideedriver.card by using the right path to the forcing files before launching simulation.c) be careful about the calendar type for different forcing files. 
    136139 
    1371402) The number of MPI is 63 in the config.card by default if using WFDEI 0.5 degree, and it is smaller if using CRU 2degree. So the users should choose the right forcing files for their simulation firstly, and then use a good MPI number.