Changes between Version 24 and Version 25 of LMDZoGuOR
- Timestamp:
- 04/27/11 16:27:14 (14 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
LMDZoGuOR
v24 v25 3 3 4 4 5 LMDZOR_v4 is the current version using LMDZ and ORCHIDEE. It is a configuration in phase with the coupled model IPSL -CM5. It can be used with LMDZ4 production version LMDZ4_AR5 or with one of the latest versions of LMDZ5/trunk.5 LMDZOR_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. 6 6 Before running this model set up, choose between 2 mode : Interannual AMIP simulation or climatologic 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. 7 7 ---- … … 14 14 }}} 15 15 16 or for clim tology AMIP :16 or for climatology AMIP : 17 17 {{{ 18 18 ln -s config.card_Climat config.card; cd COMP; ln -s lmdz.card_Climat lmdz.card … … 25 25 26 26 '''Step 1''' [[BR]] 27 Identify time series for the simulations you want and split them into yearly files. For the SST use the variable tsol_oce from LMDZ and for SIC use the variable pourc_sic. The variables should be at monthly time serie format. For exemple for the coupled IPSLCM5A rcp4.5 simulation, at CCRT use files :27 Identify time series for the simulations you want and split them into yearly files. For the SST use the variable tsol_oce from LMDZ and for SIC use the variable pourc_sic. The variables should be at monthly time series format. For example for the coupled IPSLCM5A rcp4.5 simulation, at CCRT use files : 28 28 {{{ 29 29 /dmnfs/cont003/p86denv/IGCM_OUT/IPSLCM5A/PROD/rcp45/v3.rcp45.1/ATM/Analyse/TS_MO/v3.rcp45.1_20060101_21251231_1M_tsol_oce.nc … … 61 61 62 62 = LMDZOR experience for running the gcm = 63 This configuration only contains only one directory for running the gcm.e : LMDZOR. This directory can be used for different type of simulation for ex emple AMIP interannual or climatolical 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 :63 This 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 : 64 64 {{{ 65 65 cd LMDZOR/COMP; ln -s lmdz.card_Climat lmdz.card; ln -s orchidee.card_Climat orchidee.card … … 72 72 The 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. 73 73 74 Paramet res in config.card such as !JobName, !CalendarType, !DateBegin, !DateEnd must always be considered and eventally modified according to desired experience.74 Parameters in config.card such as !JobName, !CalendarType, !DateBegin, !DateEnd must always be considered and eventually modified according to desired experience. 75 75 76 76 ---- … … 80 80 * 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 : 81 81 '''''ERROR: 0032-184 MPI was not finalized in routine unknown, task 0''''' 82 * 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 t mpi_openmpi. In your job, add '''@ parallel_threads = 8'''. This gives you 8 times more memory per process mpi availible 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 :82 * 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 : 83 83 84 84 {{{ … … 91 91 }}} 92 92 93 * You must de sactivate the filtrefft if using branch LMDZ4_AR5 or earlier version of LMDZ. In run.def set '''use_filtre_fft = n'''.93 * You must deactivate the filter fft if using branch LMDZ4_AR5 or earlier version of LMDZ. In run.def set '''use_filtre_fft = n'''. 94 94 95 95 * In config.card you must change to … … 113 113 114 114 1) Create file grilles_gcm.nc[[BR]] 115 LMDZ contains a program that creates a file netcdf contain g the grid u and v. This program is located in file LMDZ5/libf/dyn3d/grilles_gcm_netcdf.F. Compile this program with the same resolution as the gcm. For exemple if using the LMDZOR_v4/Makefile, add in Makefile :115 LMDZ contains a program that creates a file netcdf containing the grid u and v. This program is located in file LMDZ5/libf/dyn3d/grilles_gcm_netcdf.F. Compile this program with the same resolution as the gcm. For example if using the LMDZOR_v4/Makefile, add in Makefile : 116 116 117 117 {{{ … … 139 139 140 140 == Interpolation using a patch in libIGCM == 141 Interpolation is done in the CREATE job at the same time as execution of create_etat0_limit for creation of bou dary files limit.nc. Using lmdz.card_Interannuel and config.card_Interannuel is necessary to interpolate over several years. libIGCM tag v1_10 is requierd. [[BR]]141 Interpolation is done in the CREATE job at the same time as execution of create_etat0_limit for creation of boundary files limit.nc. Using lmdz.card_Interannuel and config.card_Interannuel is necessary to interpolate over several years. libIGCM tag v1_10 is requierd. [[BR]] 142 142 143 143 To activate the patch modifications in CREATE/COMP/lmdz.card_Interannuel is needed. Add the files to interpolate in [!BoundaryFiles]/List and in [!OutputFiles]/List and add the paragraf [Nudge_Interp] in the end of lmdz.card. Here below is an exemple how to add u. In the same lmdz.card it is possible to add different files u,v,t,... using the same syntax :