Changes between Initial Version and Version 1 of LMDZOR_v4


Ignore:
Timestamp:
04/28/11 15:34:28 (11 years ago)
Author:
jgipsl
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • LMDZOR_v4

    v1 v1  
     1[[PageOutline]] 
     2 
     3= LMDZOR_v4 configuration =  
     4Josefine Ghattas[[BR]] 
     5 
     6LMDZOR_v4 is the current version using LMDZ and ORCHIDEE. It is a configuration in phase with the coupled model IPSLCM5A. It can be used with LMDZ4 production version LMDZ4_AR5 or with one of the latest versions of LMDZ5/trunk.  
     7Before running this model set up, choose between 2 mode : Interannual AMIP simulation or climatological simulation. No default setup exists. Modifications done by the user in the lmdz.card or orchidee.card are often necessary to adapt to a specific simulation. Modifications in lmdz.driver or orchidee.driver are less often necessary.  
     8---- 
     9 
     10= CREATE experience for creation of initial state and interpolating of boundary conditions = 
     11This experience is used to interpolate boundary conditions(limit.nc and climoz_LMDMZ.nc) and create initial state conditions (start.nc and startphy.nc) for LMDZ using the executable ce0l.e or create_etat0_limit.e. The CREATE experience does not contain a PARAM directory. Instead in CREATE/COMP/lmdz.card the parameter ''PARAM_DIR'' points to the directory in experience LMDZOR. PARAM_DIR can be changed to use another directory if wanted.  
     12 
     132 cases for the boundary conditions are predefined : creation using sea-surface temperature(SST) and sea-ice cover(SIC) from climatology AMIP files or from interannual AMIP files. According to the case you want, copy or link the corresponding .cards. For climatology AMIP : 
     14{{{ 
     15ln -s config.card_Climat config.card; cd COMP; ln -s lmdz.card_Climat lmdz.card 
     16}}} 
     17or for interannual AMIP : 
     18{{{ 
     19ln -s config.card_Interannuel config.card; cd COMP; ln -s lmdz.card_Interannuel lmdz.card 
     20}}} 
     21 
     22== Using IPSL coupled model output == 
     23 
     24Do following steps to create boundary conditions using output from a previous LMDZ run.[[BR]] 
     25 
     26NB: it is not possible to use version LMDZ4_AR5 of ce0l. Use version LMDZ5/trunk revision 1508 or later. Once the boundary files limit.nc are created they can be used also with earlyer versions of LMDZ such as LMDZ4_AR5. 
     27 
     28'''Step 1''' [[BR]] 
     29Identify time series for the simulations you want and split them into yearly files. For the SST use the variable tsol_oce and for SIC use the variable pourc_sic. The variables should be at monthly time series format from LMDZ. For example for the coupled IPSLCM5A rcp4.5 simulation, at CCRT use the files : 
     30{{{ 
     31/dmnfs/cont003/p86denv/IGCM_OUT/IPSLCM5A/PROD/rcp45/v3.rcp45.1/ATM/Analyse/TS_MO/v3.rcp45.1_20060101_21251231_1M_tsol_oce.nc 
     32/dmnfs/cont003/p86denv/IGCM_OUT/IPSLCM5A/PROD/rcp45/v3.rcp45.1/ATM/Analyse/TS_MO/v3.rcp45.1_20060101_21251231_1M_pourc_sic.nc 
     33}}} 
     34Use cdo to split the time series into yearly files with 12 time steps in each file. For exemple : 
     35{{{ 
     36cdo splityear TS_MO_tsol_oce  $WORKDIR/my_new_dir/v3.rcp45.1_tsol_oce_ 
     37cdo splityear TS_MO_pourc_sic $WORKDIR/my_new_dir/v3.rcp45.1_pourc_sic_ 
     38}}} 
     39 
     40'''Step 1 bis''' 
     41If you want to create anomaly SST instead of direct model output SST : do it now. Description to come. 
     42 
     43'''Step 2'''[[BR]] 
     44The yearly files are now directly usable with the ce0l program revision 1508 LMDZ5/trunk or later. They should be renamed as histmth_sst.nc and histmth_sic.nc before running. The AMIP files must not be in the same run directory, in that case they will be used instead of the model output files. Use the CREATE interannual experience to create the boundary conditions for the interval of years needed. Change in lmdz.card_Interannual AMIP yearly files towards yearly time series : 
     45{{{ 
     46[BoundaryFiles] 
     47List=   (${R_INIT}/ATM/${config_UserChoices_TagName}/AMIP/amipbc_sst_360x180_${year}.nc, amipbc_sst_1x1.nc), \ 
     48        (${R_INIT}/ATM/${config_UserChoices_TagName}/AMIP/amipbc_sic_360x180_${year}.nc, amipbc_sic_1x1.nc), \ 
     49}}} 
     50into 
     51{{{ 
     52[BoundaryFiles] 
     53List=   (/the/whole/path/to/the/yearly/files_tosl_oce_${year}.nc,  histmth_sst.nc), \ 
     54        (/the/whole/path/to/the/yearly/files_pourc_sic_${year}.nc, histmth_sic.nc), \ 
     55}}} 
     56 
     57Modify the period in config.card_Interannual. Don't forget to copy or link the lmdz.card_Interannal into lmdz.card and config.card_Interannual into config.card. Submit the experience. 
     58 
     59 
     60== Interpolation of nudge files == 
     61The files that will be used for the nudging (''fr'' guidage) must be interpolated to the model grid before running the gcm. Scripts to do this are stored in directory CREATE/SCRIPT. To interpolate ERA-Interim use the script interp_from_era.ksh. You must first modify the beginning of this script. To interpolate LMDZ model output files use the script interp_from_TS.ksh. Both scripts depend on the script era2gcm.ksh. These script access the archive directory with a use in ferret. Therefore it is not possible to use them from vargas or brodie. These scripts are tested at mercure and ulam. Follow step 1 to 3 :  
     62 
     631) Create file grilles_gcm.nc[[BR]] 
     64The file grilles_gcm.nc is created by default during the CREATE experience '''if''' you use revision 1508 of LMDZ5/trunk or later and revision 1333 or later of the configuration LMDZOR_v4.  
     65The file grilles_gcm.nc contains the different grids used as target for the interpolation. The file is created with ce0l if the parameter grille_gcm_netcdf=T(default in CREATE). After a normal CREATE experience the file can be found in the archive directory IGCM_OUT/LMDZOR/ELXXXX/ATM/Output/Boundary/. If the grid contains a zoom it is important that the file grilles_gcm.nc is created at the same time as the other boundary conditions and initial state files, using the same .def parameter files describing the grid. 
     66 
     672) Modify and run the script interp_from_era.ksh from a machine that access the ERA files by use in ferret. Script tested at mercure and ulam. [[BR]] 
     68 
     693) Move interpolated files to archive directory.[[BR]] 
     70---- 
     71 
     72= LMDZOR experience for running the gcm = 
     73This configuration only contains only one directory for running the gcm.e : LMDZOR. This directory can be used for different type of simulation for example AMIP interannual or climatological run. Or nudged run with regular or zoomed grid. Only the .card changes for different run. The PARAM directory and the .driver are the same. Two possibilities are predefined using the different .cards that are available. To do a climatological simulation, use cards with suffix ''_Climat'', do following link : 
     74{{{ 
     75cd LMDZOR/COMP; ln -s lmdz.card_Climat lmdz.card; ln -s orchidee.card_Climat orchidee.card 
     76}}} 
     77Or to do an AMIP interannual simulation use cards with suffix ''_AMIP'', do following link : 
     78{{{ 
     79cd LMDZOR/COMP; ln -s lmdz.card_AMIP lmdz.card; ln -s orchidee.card_AMIP orchidee.card 
     80}}} 
     81 
     82The cards with suffix _Climat correspond to the experience LMDZOR in configuration LMDZ4OR_v3 and the cards with suffix _AMIP correspond to the experience in directory AMIP in LMDZ4OR_v3 configuration. 
     83 
     84Parameters in config.card such as !JobName, !CalendarType, !DateBegin, !DateEnd must always be considered and eventually modified according to desired experience. 
     85 
     86== Nudged run == 
     87Follow 3 steps to activate nudging in LMDZ. [[BR]] 
     88 
     891) Set parameter ok_guide=y in lmdz.card. [[BR]] 
     90 
     912) Modify parameter file guide.def containing specifications for the nudging according to the experience.[[BR]] 
     92 
     933) 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.  
     94 
     95---- 
     96 
     97= Problems running at VARGAS = 
     98 * You should not compile with -O5 at VARGAS. Compile with -O3 or lower optimization. Default compiler xlf 13.1.0.3 is ok with -O3. 
     99 * If the executable create_etat0_limit or ce0l exits with following error message you need to update your LMDZ version to revision 1476 at branch LMDZ4_AR5 or higher : 
     100'''''ERROR: 0032-184 MPI was not finalized  in routine unknown, task 0''''' 
     101 * Check memory in your job. For higher resolutions you may need to add threads just to have more memory. You must then compile in mpi mode (default for create_etat0_limit.e.para) and not mix mpi_openmpi. In your job, add '''@ parallel_threads = 8'''. This gives you 8 times more memory per process mpi available and you can multiply data_limit and stack_limit by 8. When adding threads you should remove '''@ resources = !ConsumableCpus(1)'''. For exemple for resolution 280x280x39 put in your job : 
     102  
     103{{{ 
     104# @ total_tasks = 32 
     105# @ environment = "BATCH_NUM_PROC_TOT=32" 
     106# @ parallel_threads = 8 
     107# @ data_limit  = 18.0gb 
     108# @ stack_limit = 6.0gb,6.0gb 
     109### @ resources = ConsumableCpus(1) 
     110}}} 
     111 
     112 * You must deactivate the filter fft if using branch LMDZ4_AR5 or earlier version of LMDZ. In run.def set '''use_filtre_fft = n'''. 
     113 
     114 * In config.card you must change to  
     115{{{ 
     116JobRunOptions='' 
     117}}} 
     118 otherwise you'll have following error message : 
     119 
     120'''ERROR: 0031-636  User requested or EOF termination of pm_command''' 
     121 
     122 
     123 
     124----