Changes between Version 116 and Version 117 of Documentation/Forcings


Ignore:
Timestamp:
2021-02-11T12:56:32+01:00 (3 years ago)
Author:
xnwang
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • Documentation/Forcings

    v116 v117  
    104104A long discussion on the differences between the two drivers (dated in 2016) can be found on https://forge.ipsl.jussieu.fr/orchidee/wiki/Branches/Driver_Improvements. 
    105105 
    106 The work on the new driver has been picked up since July 2020. 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. 
    107  
     106The 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. 
     107 
     108A summary of recent progress on the integraton of new driver in the trunk (until the end of 2020): 
     109 
     110* the recent version of new driver from Jan. P is included in the trunk  
     111* fixed a bug when using the forcing file of coarse resolution: corresponding to the ticket https://forge.ipsl.jussieu.fr/orchidee/ticket/575 
     112* 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. 
     113* identified that the old and the new drivers have the reversed order of latitude when writing the restart file 
     114 
     115Several codes or files were modified and a new script added: 
     116 
     117* fortran code: significant modification to src_driver/forcing_tools.f90, slight change to src_driver/orchideedriver.f90 
     118* libIGCM : libIGCM/libIGCM_config/libIGCM_config.ksh 
     119* configuration files: COMP/orchideedriver.driver , PARAM/run.def , PARAM/orchidee.def : routing=n (in the tests by using forcing files of coarse resolution) 
     120* 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). 
     121 
     122 
     123A few remarks in the blow for the knowledge of users of the new driver: 
     124 
     1251) The new driver need the forcing files of previous, current, and next year. 
     126        Suppose that we have forcing files over 1860-2012 and we need run a simulation with the same period, we need forcing files for 1859 and 2013 when using the new driver. The script AddYears is to prepare for such forcing files. 
     127        * 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. 
     128        * 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 .card by using the right path to the forcing files before launching simulation. 
     129 
     1302) 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.  
     131 
     132                   
    108133 
    109134