Changes between Version 26 and Version 27 of Documentation/Drivers


Ignore:
Timestamp:
10/01/21 15:51:34 (4 months ago)
Author:
xnwang
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • Documentation/Drivers

    v26 v27  
    4848* In spring 2021, Matt mentioned the speed of simulation by using the new driver, compared to the old one. Some profiling tests were applied to the simulations by using new and old drivers. In PARAM/run.def, dt_sechiba =1200 was found to be responsible for most of the slowness of the new driver. The value of this parameter depends on user's need. The smaller value, the slower computation, but with more time steps during the simulation. 
    4949* In summer 2021, a new ticket http://forge.ipsl.jussieu.fr/orchidee/ticket/786 was submitted concerning a problem of the new driver when using the compressed forcing file. By using the latest version of compressed forcing file CRU JRA v2.2, small modification were applied and tested. The new driver now works with the compressed forcing file such as CRU JRA 0.5 degree. But it does not work with the older version of CRU JRA v2.1 0.5 degree , due to some inconsistency between land variable and contfrac in the forcing data.  
    50 * In summer 2021, the new driver in Tag 2.2 is updated by Agnes.  
    51  
     50* The new driver in Tag 2.2 is updated by Agnes in summer 2021. 
     51* Simulation tests were made with trunk (spinup 50 years, fg1trans and fg2 10 years) by using CRU JRA v2.2 and new driver. Identified a few minor errors about : 1) the format of 1900-year forcing file in 0.5deg and 2deg CRU JRA v2.2, 2) libIGCM version in mod.def, 3) config.card for spinup. The corrections were committed to r7296. 
    5252 
    5353'''Useful information for the users of the new driver:''' 
     
    5858        * 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).  
    5959 
    60 2) 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.  
     602) The number of MPI is 64 in the config.card by default if using WFDEI 0.5 degree, and it is 32 if using CRU 2degree. So the users should choose the right forcing files for their simulation firstly, and then use a good MPI number.  
    6161 
    62623) in PARAM/orchidee.def: if we use forcing file of coarse resolution, it would be better to set RIVER_ROUTING = n to avoid possible routing errors. 
    6363 
    64 4) The users need update also libIGCM (if they did not do so) before running the new driver. 
     644) The users might need to update libIGCM before running the new driver in other Tags than trunk. 
    6565 
    6666                   
     
    6868 
    6969* to test the new driver in the recent version of trunk by running spinup analytic, fg1transnd and fg2nd.  
    70    The comparisons of FG1 can be found at https://orchidas.lsce.ipsl.fr/mapper/?set=Milestone-4.1&mode=FG1 (thanks to Vlad) 
     70   The previous comparisons of FG1 can be found at https://orchidas.lsce.ipsl.fr/mapper/?set=Milestone-4.1&mode=FG1 (thanks to Vlad) 
    7171 
    7272