Changes between Version 13 and Version 14 of Doc/Models/LMDZ


Ignore:
Timestamp:
10/05/15 15:17:08 (9 years ago)
Author:
lfairhead
Comment:

--

Legend:

Unmodified
Added
Removed
Modified

  • Doc/Models/LMDZ

    v13 v14  
    1616 
    1717# Resolutions # 
    18 The following resolutions are available: 56x55x19, 96x71x19, 96x95x19, 96x95x39, 144x142x19, 144x142x39. However only the resolutions 96x95x39(also called LR : low resolution) and 144x142x39(MR : mid resolution) are equilibrated in coupled simulations and fully tested. If you want to add a new resolution you must create the GENERAL/PARAM/gcm.def_resol file. If the vertical resolution changes you must also add the corresponding physiq.def_ file.  
    19  
    20 If you use LMDZ in forced mode with or without ORCHIDEE, you must once create boundary condition files for the chosen resolution, [wiki:DocImodelBlmdz#Creatinginitialstatesandinterpolatingboundaryconditions see below]. 
     18The following resolutions are available: 56x55x19, 96x71x19, 96x95x19, 96x95x39, 144x142x19, 144x142x39, 144x142x79. However only the resolutions 96x95x39(also called LR : low resolution) and 144x142x39(MR : mid resolution) are equilibrated in coupled simulations and fully tested. If you want to add a new resolution you must create the GENERAL/PARAM/gcm.def_resol file. If the vertical resolution changes you must also add the corresponding physiq.def_ file.  
     19 
     20If you use LMDZ in forced mode with or without ORCHIDEE, you must create boundary condition files for the chosen resolution once before starting the simulation, [wiki:DocImodelBlmdz#Creatinginitialstatesandinterpolatingboundaryconditions see below]. 
    2121 
    2222# Restart files and boundary conditions # 
    … …  
    3939## Creating initial states and interpolating boundary conditions ##  
    4040 
    41 Once you chose and installed your configuration, you will find the config.card and lmdz.card files in the modipsl/config/.../EXPERIMENTS/LMDZ/CREATE_''xxx'' directories. These files allow you to prepare jobs that create restarts and boundary conditions from initial files located on shared accounts. The jobs follow the classical procedure explained in [wiki:/DocEsetup Chapter 3: Simulation setup]. The files found in the directories are: 
     41Once you have chosen and installed your configuration, you will find the config.card and lmdz.card files in the modipsl/config/.../EXPERIMENTS/LMDZ/CREATE_''xxx'' directories. These files allow you to prepare jobs that create restarts and boundary conditions from initial files located on shared accounts. The jobs follow the classical procedure explained in [wiki:/DocEsetup Chapter 3: Simulation setup]. The files found in the directories are: 
    4242 
    4343 CREATE_clim:: 
    44     allow to create boundary conditions with climatological SSTs 
     44    creates boundary conditions with climatological SSTs 
    4545 CREATE_amip:: 
    46     allow to create interannual AMIP boundary conditions 
    47  
    48 [[NoteBox(warn, You must properly define the same calender ''leap/noleap/360d'' in config.card of the job that creates initial states and in config.card of the job that starts your experiment.,600px)]] 
    49  
    50  
    51 __Note :__ If you want to use datasets other than AMIP you must change the `lmdz.card` file in the experiment CREATE_xxxx choisi and maybe also in the LMDZ model. 
     46    creates interannual AMIP boundary conditions 
     47 
     48[[NoteBox(warn, You must properly define the same calendar ''leap/noleap/360d'' in config.card of the job that creates initial states and in config.card of the job that starts your experiment.,600px)]] 
     49 
     50 
     51__Note :__ If you want to use datasets other than AMIP you must change the `lmdz.card` file in the experiment CREATE_xxxx chosen. 
    5252 
    5353 
    5454 
    5555## Using the coupled IPSL model outputs ## 
    56 Follow the steps below to create the limit.nc files of a previous LMDZ simulation (coupled or forced). [[BR]] 
    57  
    58 Note: ce0l of LMDZ4_AR5 can not be used. Use instead LMDZ5/trunk revision 1508 or a later revision. Once the limit.nc files created, LMDZ4_AR5 or LMDZ5 can be used.  
     56Follow the steps below to create the limit.nc files from the data of a previous LMDZ simulation (coupled or forced). [[BR]] 
     57 
     58Note: the ce0l program from LMDZ4_AR5 cannot be used. Instead, use the LMDZ5/trunk 1508, or later, revision 1508. Once the limit.nc files are created, LMDZ4_AR5 or LMDZ5 can be used.  
    5959 
    6060'''Step 1''' [[BR]] 
    … …  
    7272 
    7373'''Step 2'''[[BR]] 
    74 The annual files can now be used directly with the ce0l script (revision 1508) LMDZ5/trunk or more recent. The files must be renamed histmth_sst.nc and histmth_sic.nc in the execution directory. The AMIP files must not be in the execution directory because they will be used first.  
     74The annual files can now be used directly with the ce0l program (revision 1508 or later) LMDZ5/trunk. The files must be renamed histmth_sst.nc and histmth_sic.nc in the execution directory. The AMIP files must not be in the execution directory because they will be used first.  
    7575 
    7676Use EXPERIMENT/LMDZ/CREATE_amip. Change it to use those new files instead of the AMIP files:  
    … …  
    9999For example, you can use the SST from a historical simulation and the AMIP SST for the period 1979-2005. You can compute the difference and apply it to any period of the future RCP 4.5 simulation. [[BR]] 
    100100 
    101 In order to do so, you can use the create_sst_anomaly.ksh script (or use it as an example) instead of the Step 1 above. Afterwards continue with Step 2 above.  
     101In order to do so, you can use the create_sst_anomaly.ksh script (or use it as an example) instead of  Step 1 above. Afterwards continue with Step 2 from above.  
    102102 
    103103The script is here: [[BR]] 
    … …  
    117117---- 
    118118# Parallelism and the ''Bands'' file # 
    119 The parallel LMDZ model with the MPI library. You will find more information on the parallelism [http://lmdz.lmd.jussieu.fr/developpeurs/notes-techniques/ressources/parallelisme-LMDZ.pdf here]. 
     119The LMDZ model in parallel mode uses the MPI library. You will find more information on the parallelism [http://lmdz.lmd.jussieu.fr/developpeurs/notes-techniques/ressources/parallelisme-LMDZ.pdf here]. 
    120120 
    121121## Maximum number of processes ## 
    … …  
    145145[[NoteBox(warn,It is not (yet) possible to run with adjust=y in 'full' hybrid MPI/OpenMP mode. Therefore you will need to make a pre-run (using either a MPI only compiled executable or a hybrid executable but executed with only one OpenMP task) to create the Bands file and then run your 'full' hybrid simulation using this Bands file. , 600px)]] 
    146146 
    147 [[NoteBox(warn,To make sure to obtain the same results between two simulations\, you must cancel the adjustment and the creation of Bands files. For the two simulations you must use the '''same''' `Bands` file., 600px)]] 
    148  
    149 [[NoteBox(warn,With INCA you can't run with adjust=y (the simulation will be wrong) so you need to make a pre-run to create the Bands file and then run your simulation by linking this file, 600px)]] 
     147[[NoteBox(warn,To make sure to obtain the same results between two simulations\, you must cancel the adjustment and the creation of Bands files. You must use the '''same''' `Bands` file for the two simulations., 600px)]] 
     148 
     149[[NoteBox(warn,With INCA you cannot run with adjust=y (the simulation will be wrong) so you need to make a pre-run to create the Bands file and then run your simulation by linking this file, 600px)]] 
    150150 
    151151---- 
    … …  
    181181ByPass_hgardfou_teta=(y/n) 
    182182}}} 
    183 This parameter allows you to divide by two dissipation times used by LMDZ on the next simulation period (1 month in general) in order to try to overcome a bug.  
     183This parameter allows you to divide by two dissipation times used by LMDZ on the next simulation period (1 month in general) in order to try to overcome a model crash.  
    184184[[BR]] 
    185185 
    … …  
    187187ByPass_hgardfou_mats=(y/n) 
    188188}}} 
    189 This parameter allows you to choose the matsuno temporal scheme (rather than leapfrog) on the next simulation period in order to try to overcome an LMDZ bug.  
     189This parameter allows you to choose the matsuno temporal scheme (rather than leapfrog) on the next simulation period in order to try to overcome a model crash.  
    190190 
    191191 
    … …  
    195195LMDZ_Bands_file_name= 
    196196}}} 
    197 LMDZ_NbPeriod_adjust determines the number of simulation periods (3 in general) during which LMDZ allocates as best as possible the parallel domains on the number of chosen processors in order to have a proper load equilibrium. During those periods adjust=y will be stored in run.def and later it will be adjust=n. [[BR]] 
     197LMDZ_NbPeriod_adjust determines the number of simulation periods (3 in general) during which LMDZ allocates as best as possible the parallel domains on the number of chosen processors in order to have proper load equilibrium. During those periods adjust=y will be stored in run.def and later it will be adjust=n. [[BR]] 
    198198 
    199199The LMDZ_Bands_file_name parameter is optional. It can indicate an equilibrium file (''bands'' file) already created with its entire path on the storage server. For this option to be taken into account you must also specify LMDZ_NbPeriod_adjust=0.[[BR]] 
    … …  
    210210Set !ConfType=preind for constant preindustrial values or !ConfType=actuel for constant present-day values choose. [[BR]] 
    211211 
    212 For annual values choose !ConfType=annuel and add the following input text files containing the yearly values : SOLARANDVOLCANOES.txt, CO2.txt, CH4.txt, N2O.txt, CFC11.txt, CFC12.txt. The file config.def_annual contains only the key word AUTO for the solar constant and the greenhouse gases. lmdz.driver will substitute AUTO with the values from the files. The syntax of these files are always the same. See here an example  : 
     212For annual values choose !ConfType=annuel and add the following input text files containing the yearly values : SOLARANDVOLCANOES.txt, CO2.txt, CH4.txt, N2O.txt, CFC11.txt, CFC12.txt. The file config.def_annual contains only the key word AUTO for the solar constant and the greenhouse gases. lmdz.driver will substitute AUTO with the values from these files. The syntax of these files are always the same. See here an example  : 
    213213{{{ 
    214214> cat CO2_1765_2005.txt 
    … …  
    270270}}} 
    271271allows you to activate the LMDZ nudging(fr guidage) by wind, temperature and humidity fields. 
    272 '''Be careful''' the fields used for nudging must be specified in the section !BoundaryFiles. The nudging files must be at the same horizontal grid as the model. Use the variables year and month for coping these files. The parameter file PARAM/guide.def will be used and you can adapt it as you need. [[BR]][[BR]] 
     272'''Be careful''' the fields used for nudging must be specified in the section !BoundaryFiles. The nudging files must be on the same horizontal grid as the model. Use the variables year and month for copying these files. The parameters contained in file PARAM/guide.def control the nudging used during the simulation and you can adapt that file as needed. [[BR]][[BR]] 
    273273 
    274274For example, set in lmdz.card : 
    … …  
    297297 * 6    all aerosols 
    298298 
    299 When flag_aerosol > 0 you must provide aerosol files to the model. In any case, the file '''aerosols.nat.nc''' is needed. Another flag '''aer_type''' determines which aerosols are taken into account. If `aer_type` is set to  "preind" preindustrial aerosols are used and only the file aerosols.nat.nc must be provided to the model. If the flag is set to  "actuel" present-day aerosols are used with the aerosols1980.nc file. If the flag is set to  "scenario" the aerosols follow a scenario with files such as aerosolsXXXX.nc with a 10-year resolution. Finally, if the flag is set to "annuel" the aerosols are taken for a specific year and the input file is aerosolsXXXX.nc where XXX is the year in the run.  
    300 [[BR]] 
    301 In case flag_aerosol > 0 both flags '''ok_ade''' and '''ok_aie''' (set to y or n) control the activation of direct and indirect (respectively) aerosol effects. In case an effect is deactivated natural aerosols are used for this effect. The flags ok_ade and ok_aie are independent from each other. However flag_aerosol must be > 0 as soon as one of the two flags ok_ade and ok_aie is activated. This also activates the radiative forcing diagnostics (topswad and topswai variables). In case ok_aie is activated you must choose the explicit computation of the cloud droplet number concentration (CDNC) with the flag '''ok_cdnc=y'''. In the opposite case you can choose ok_cdnc=y (CDNC is computed explicitly from an empirical relationship which depends on aerosols) or ok_cdnc=n (an effective radius is then directly prescribed). 
     299When flag_aerosol > 0 you must provide aerosol files to the model. In all cases, the file '''aerosols.nat.nc''' is needed. Another flag '''aer_type''' determines which aerosols are taken into account. If `aer_type` is set to  "preind", preindustrial aerosols are used and only the file aerosols.nat.nc must be provided to the model. If the flag is set to  "actuel" present-day aerosols are used with the aerosols1980.nc file. If the flag is set to  "scenario" the aerosols follow a scenario with files such as aerosolsXXXX.nc with a 10-year resolution. Finally, if the flag is set to "annuel" the aerosols are taken for a specific year and the input file is aerosolsXXXX.nc where XXX is the year in the run.  
     300[[BR]] 
     301If flag_aerosol > 0 both flags '''ok_ade''' and '''ok_aie''' (set to y or n) control the activation of direct and indirect (respectively) aerosol effects. In case an effect is deactivated, natural aerosols are used for this effect. The flags ok_ade and ok_aie are independent from each other. However flag_aerosol must be > 0 as soon as one of the two flags ok_ade and ok_aie is activated. This also activates the radiative forcing diagnostics (topswad and topswai variables). In case, ok_aie is activated you must choose the explicit computation of the cloud droplet number concentration (CDNC) with the flag '''ok_cdnc=y'''. In the opposite case, you can choose ok_cdnc=y (CDNC is computed explicitly from an empirical relationship which depends on aerosols) or ok_cdnc=n (an effective radius is then directly prescribed). 
    302302[[BR]] 
    303303bl95_b0=1.7 and bl95_b1=0.2 are the parameters of the relationship between aerosol mass and CDNC according to the Boucher and Lohmann (1995) parametrization.  
    … …  
    344344}}} 
    345345  
    346 If you are nudging your simulation with ERAI data, is consistent to use boundaries files (limit.nc) create with ERAI data. These files are stored here (for 96x95x39):  
     346If you are nudging your simulation with ERAI data, it is consistent to use boundaries files (limit.nc) created with ERAI data. These files are stored here (for 96x95x39):  
    347347{{{ 
    348348/workgpfs/rech/psl/rpsl035/IGCM/BC/ATM/LMDZ/LMD9695/LIMIT     at ada  
    … …  
    3743742) Add files containing the nudging variables in lmdz.card (''_Climat'' or ''_AMIP'') in section !BoundaryFiles. These files have to be interpolated previously to the model horizontal grid.  
    375375 
    376 3) Most probably you have to modify parameter file guide.def containing specifications for the nudging according to your experience.[[BR]] 
    377  
     3763) Most probably you will have to modify parameter file guide.def containing specifications for the nudging according to your experiment.[[BR]] 
     377