Changes between Version 5 and Version 6 of Doc/Config/LMDZOR_v6.1


Ignore:
Timestamp:
07/09/15 19:05:37 (9 years ago)
Author:
jgipsl
Comment:

--

Legend:

Unmodified
Added
Removed
Modified

  • Doc/Config/LMDZOR_v6.1

    v5 v6  
    2424Default compilation is still 96x96x39. Default option during run time is old physics and 2-layer hydrology. These options can be changed.   
    2525 
    26 # Parameter files # 
    27 Most parameter file are found in PARAM/ directory as for the v5 configurations. But some files are now also copied from the model directories. This is the case for field_def_lmdz.xml and field_def_orchidee.xml. In lmdz.card and orchidee.card you can see where the files are taken from.  
     26## Compiling ## 
     27Default compilation is still 96x96x39 but other resolutions can be compiled. To compile 144x142x79 grid do as follow : 
    2828 
    29 In the parameter files, some of the variables will be modified after the job is submitted. All these variables are set equal _AUTO_ or _AUTOBLOCKER_. No variable can be modified without having this key word. This means that the real value will be set by the drivers when the job is submitted. The values are set according to the options from lmdz.card, orchidee.card, stomate.card and config.card.  
     29{{{ 
     30gmake LMD144142-L79 
     31}}} 
    3032 
    31 A variable which is set to _AUTO_ can also be changed manually in the corresponding file in the PARAM directory. For this case, the driver can not change it again. Some variables are set equal _AUTOBLOCKER_. They cannot be changed. If still they are changed, the job will exit with error message. 
     33By default the compiling is done for hybrid MPI and OMP parallelism. It is not necessary to activate OMP threads during run time. 
    3234 
    33 ## Controlling output ## 
     35## Launching ## 
     36 
     37The default set up is using 31MPI for the gcm.e and 1MPI for the xios server. This is set in config.card :  
     38{{{ 
     39#-- Total Number of Processors 
     40JobNumProcTot=32 
     41 
     42[Executable] 
     43ATM= (gcm.e, lmdz.x, 31MPI, 1OMP) 
     44SRF= ("", "") 
     45SBG= ("", "") 
     46IOS= (xios_server.exe, xios.x, 1MPI) 
     47}}} 
     48 
     49 
     50## XIOS and controlling output ## 
     51XIOS is the new component used for output writing. It consists of a library linked to the model and an external server executable (xios_server.exe). It can be launched in attached mode or in server mode. The default set up in LMDZOR_v6 is using the server mode with 1 MPI for the server. 2 executables are launched: gcm.e and xios_server.exe. No reconstruction is needed for the output files. The rebuild tool detects automatically that this is not needed.  
     52 
     53 
    3454LMDZOR_v6 is only using XIOS for writing diagnostic output files. The output is managed by xml files. The files beginning with file_def....xml are controlling the variables and the files that are written.  
    3555 
    36 A basic level of output control is done from config.card with the variables WriteFrequency. For LMDZ it is also possible to change the level of output for the files using the variable OutLevel in lmdz.card. Finer control of the output must be done directly in PARAM/file_def_....xml files. Where it is set _AUTO_, it can be replaced manually for exemple in PARAM/file_def_histday_lmdz.xml : 
     56 
     57A basic level of output control is done from config.card with the variables !WriteFrequency. For LMDZ it is also possible to change the level of output for the files using the variable !OutLevel in lmdz.card. Finer control of the output must be done directly in PARAM/file_def_....xml files. Where it is set _AUTO_, it can be replaced manually for example in PARAM/file_def_histday_lmdz.xml : 
    3758 
    3859{{{ 
    … …  
    4566 
    4667 
     68## Parameter files ## 
     69Most parameter file are found in PARAM/ directory as for the v5 configurations. But some files are now also copied from the model directories. This is the case for field_def_lmdz.xml and field_def_orchidee.xml. In lmdz.card and orchidee.card you can see where the files are taken from.  
     70 
     71In the parameter files, some of the variables will be modified after the job is submitted. All these variables are set equal _AUTO_ or _AUTOBLOCKER_. No variable can be modified without having this key word. This means that the real value will be set by the drivers when the job is submitted. The values are set according to the options from lmdz.card, orchidee.card, stomate.card and config.card.  
     72 
     73A variable which is set to _AUTO_ can also be changed manually in the corresponding file in the PARAM directory. For this case, the driver can not change it again. Some variables are set equal _AUTOBLOCKER_. They cannot be changed. If still they are changed, the job will exit with error message. 
     74 
     75 
    4776# Quick installation # 
    4877 
    … …  
    5382./model LMDZOR_v6 
    5483cd ../condig/LMDZOR_v6 
    55 gmake      [or gmake LMD144142-L39] 
     84gmake      [or gmake LMD144142-L79] 
    5685 
    5786# Experiment setup 
    58 cp EXPERIMENT/LMDZOR/clim/config.card . 
    59 => modify at least JobName=MyJobname, DateBegin, DateEnd 
     87cp EXPERIMENT/LMDZOR/clim/config.card .     # => modify at least JobName=MyJobname, DateBegin, DateEnd in config.card 
    6088../../util/ins_job 
    6189cd MyJobname 
    62 # Modify default setup: change physics in lmdz.card (for other physics dans AP or NPv3.2 you also need to add physic.def_NPxxx in PARAM/) 
     90 
     91# Modify default setup: change physics in lmdz.card (for other physics than AP or NPv3.2 you also need to add physic.def_NPxxx in PARAM/) 
    6392# change hydrology(2- or 11- layer) in orchidee.card 
    6493ccc_msub Job_MyJobname / llsubmit Job_MyJobname