Changes between Version 3 and Version 4 of Documentation/Drivers


Ignore:
Timestamp:
2021-03-11T17:53:26+01:00 (3 years ago)
Author:
xnwang
Comment:

--

Legend:

Unmodified
Added
Removed
Modified

  • Documentation/Drivers

    v3 v4  
    3636The work on the new driver has been picked up since July 2020 by X. W. A short report summarizes the first part of this efforts and can be found on https://forge.ipsl.jussieu.fr/orchidee/attachment/wiki/Documentation/Forcings/nouveau_driver_doc.2.pdf. 
    3737 
    38 '''Summary of recent progress ''' on the integraton of new driver in the trunk (until the end of 2020): 
     38'''More efforts and progress ''' on the integraton of new driver in the trunk, updated in March 2021: 
    3939 
    40 * the recent version of new driver from Jan. P is included in the trunk  
     40* the recent version of new driver from Jan. P is included in the trunk. This is committed in r7082. 
    4141* fixed a bug when using the forcing file of coarse resolution: corresponding to the ticket https://forge.ipsl.jussieu.fr/orchidee/ticket/575 
    42 * modified several places in orchidee in order that the new driver can be used not only for FG3, but also for spinup analytic and fg1trans. 
     42* in order to use new driver for spinup and fg1trans as well, modified src_driver/forcing_tools.f90 significantly, slight change to src_driver/orchideedriver.f90 
     43* for the same purpose, modified libIGCM/libIGCM_config/libIGCM_config.ksh and several places in orchidee configuration files, so that the new driver works for not only FG2, but also spinup and fg1trans. These changes are committed into r7082. 
    4344* identified that the old and the new drivers have the reversed order of latitude when writing the restart file 
    44  
    45 '''Codes or files modified or added:''' 
    46  
    47 * fortran code: significant modification to src_driver/forcing_tools.f90, slight change to src_driver/orchideedriver.f90 
    48 * libIGCM : libIGCM/libIGCM_config/libIGCM_config.ksh 
    49 * 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) 
    50 * 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). 
     45* created FG2nd for using the new driver, in order to be consistent with FG2. This is committed in r7112. 
     46* updated all the configuration files (spinup analystique, fg1trans, fg2, fg8) in the recent version of trunk by using the new driver, and tested them with global simulation over a few years. After the tests, these updates are committed in r7119 of trunk. Fixed the ticket http://forge.ipsl.jussieu.fr/orchidee/ticket/730 
     47* added a new script AddYears in TOOLS/newdriver for ORCHIDEE , useful for preparing the forcing file when using the new driver. This is committed in r7112. 
     48* created extra forcing file for using new driver and added them into the IGCM repository  
    5149 
    5250 
    … …  
    55531) The new driver need the forcing files of previous, current, and next year. 
    5654        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. 
    57         * 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. 
    58         * 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. 
     55        * Most recent forcing files now have extra forcing files in the default IGCM 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 are already included in the experiment folder. 
     56        * If a user need older version of forcing files, he/she may 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. This script has been tested with CRUJRA (two deg and half deg of of recent version), WFDEI, CRU-NCEP (two deg and one deg).  
    5957 
    60 2) 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.  
     582) The number of MPI is 63 in the config.card by default if using WFDEI 0.5 degree, and it is 31 if using CRU 2degree. So the users should choose the right forcing files for their simulation firstly, and then use a good MPI number.  
    6159 
    62603) in PARAM/orchidee.def: if we use forcing file of coarse resolution, it would be better to set RIVER_ROUTING = n to avoid possible errors. 
    6361 
     62 
    6463                   
    65 '''A few more things to do:''' 
     64'''A few more things probably need to do:''' 
    6665 
    6766* to make sure of the complete integration of the new driver in the recent version of trunk (libIGCM, script)