Changes between Version 23 and Version 24 of Doc/Running
- Timestamp:
- 09/24/15 18:22:34 (9 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Doc/Running
v23 v24 11 11 ---- 12 12 13 # Diagram of the jobs executed by the IPSL running environment#13 # Overview of IPSL running environment workflow # 14 14 The main computing job automatically runs post processing jobs (at different frequencies) during the simulation. Here is a diagram describing the job sequence: 15 15 … … 240 240 241 241 ## Rebuild ## 242 * `rebuild` is a tool which allows you to combine several files created by a parallel program (sub domains) to a single file. 242 * `rebuild` is a tool which allows you to combine several files created by a parallel program (sub domains) to a single file. Note that if you use XIOS as output library (XIOS is used in v6 configurations), the rebuild step could not be needed : it depends on the writing mode (parallel or not, server or not) you have activated. 243 243 * `rebuild` is available with IOIPSL package. See http://forge.ipsl.jussieu.fr/igcmg/browser/IOIPSL/trunk/tools (it can therefore be distributed via modipsl) 244 244 * `rebuild` is installed on the IDRIS and TGCC front-end machines. It is automatically called at the !RebuildFrequency frequency and it is usually the very first step of post processing. … … 249 249 250 250 ## Concatenation of "PACK" outputs ## 251 The model outputs are concatenated before being stored on file servers. The concatenation frequency is set by the '''!PackFrequency''' parameter. If this parameter is not set the rebuild frequency !RebuildFrequency is used. [[BR]]252 This packing step is performed by the PACKRESTART, PACKDEBUG jobs (started by the main job) and PACKOUTPUT (started by the Rebuild job).253 254 ### How are the different kinds of output files treated ###251 The model outputs are concatenated before being stored on archive servers. The concatenation frequency is set by the '''!PackFrequency''' parameter. If this parameter is not set the rebuild frequency !RebuildFrequency is used. [[BR]] 252 This packing step is performed by the PACKRESTART, PACKDEBUG(started by the main job) and PACKOUTPUT (started by the Rebuild job) jobs. 253 254 ### How are the different kinds of output files treated ? ### 255 255 256 256 All files listed below are archived or concatenated at the same frequency (!PackFrequency) … … 278 278 279 279 * Each output file (section [!OutputFiles]) is related to a post processing job: Post_1M_histmth in the example. 280 * post_1M_histmth is a section (starting by "[Post_1M_histmth]")280 * Post_1M_histmth is a section (starting by "[Post_1M_histmth]") 281 281 * This section contains the variables : Patches= , !GatherWithInternal = , !TimeSeriesVars2D = , !ChunckJob2D , !TimeSeriesVars3D and !ChunckJob3D. 282 * Patches= (Patch_20091030_histcom_time_axis) : this is the Patch which will be applied to the output file before being stored on the file server. The available Patches can be found here: [http://forge.ipsl.jussieu.fr/libigcm/browser/trunk/libIGCM/libIGCM_post libIGCM_post] Different Patches can be applied consecutively.282 * Patches= (Patch_20091030_histcom_time_axis) : this is the Patch which will be applied to the output file. The available Patches can be found here: [http://forge.ipsl.jussieu.fr/libigcm/browser/trunk/libIGCM/libIGCM_post libIGCM_post] Different Patches can be applied consecutively. 283 283 * !GatherWithInternal = (lon, lat, presnivs, time_counter, aire) These are the variables to be extracted from the initial file and to be stored with the Time Series variable. 284 284 * !TimeSeriesVars2D/3D = those are variable lists of time series to create. … … 286 286 287 287 288 The Time Series coming from monthly (or daily) output files are stored on the file server in the IGCM_OUT/!TagName/[!SpaceName]/[!ExperimentName]/!JobName/Composante/Analyse/TS_MO and TS_DA directories.288 The Time Series coming from monthly (or daily) output files are stored on the archive server in the IGCM_OUT/!TagName/[!SpaceName]/[!ExperimentName]/!JobName/Composante/Analyse/TS_MO and TS_DA directories. 289 289 290 290 … … 295 295 296 296 ## Monitoring and intermonitoring ## 297 The monitoring is a web-interface tool that visualize the global mean over time for a set up of key variables. Access the monitoring using the address for dods at your machine ending with yourlogin/TagName/SpaceName/JobName. If you have a new account, you might need to contact the assistant team at the computer center to activate your write access to dods.297 The monitoring is a web-interface tool that visualizes the global mean over time for a set up of key variables. Access the monitoring using the address for dods at your machine ending with yourlogin/TagName/SpaceName/JobName. If you have a new account, you might need to contact the assistant team at the computer center to activate your write access to dods. 298 298 * dods at TGCC: 299 299 * http://dods.extra.cea.fr/work for the old one … … 362 362 * Step 5: Now a ferret script will appear on the screen and one image. Click on the button Run this script on the server below on the page. The inter-monitoring for all variables will now appear on the screen. 363 363 364 ### How to add save the intermonitoring permanently (section under edition JG )###364 ### How to add save the intermonitoring permanently ### 365 365 The plots done by the intermonitoring will be kept 15 days. During these days you can visualize using the same link the plots done. To keep them permanently, do as follow: 366 366 * Create the intermonitoring using the webservices interface (see mini howto or audio guide above) 367 367 * Save the .jnl script and the .bash script created by the webservices to your computer, together in the same directory. 368 * Edit the .bash : beginning and in the end (to be completed). The last line contains a copy to dods. 368 * Edit the .bash and modify as follows : 369 * source of ferret configuration files. Here are examples to uncomment if needed : 370 {{{ 371 #. /home/webservices/.atlas_env_webservices_bash # IPSL (webservices) 372 #. /home/rech/psl/rpsl035/.atlas_env_ulam_bash # IDRIS (ulam) 373 #. /home/users/brock/.atlas_env_asterix_bash # LSCE (asterix) 374 #. /home/brocksce/.atlas_env_calcul_ksh # IPSL (calcul2) 375 #. /ccc/cont003/home/dsm/p86ipsl/.atlas_env_netcdf4_curie_ksh #TGCC (curie) 376 }}} 377 * define the path where you saved the .jnl script. 378 {{{ 379 scriptname=./intermonit_CM6.jnl 380 }}} 369 381 * Run the .bash script. A new directory will appear on your computer. This is the directory that is also copied to dods. 370 382 * The intermonitoring is now on dods and you can keep the link permanently. … … 378 390 379 391 ## Atlas ## 380 * The atlas is a result of the post processing, which will create a collection of plots presented as a web tree. Each plot is available as image and pdf file. The plots are made with the software ferret and the FAST and ATLAS libraries. More information on ferret and on those libraries can be found here http://wiki.ipsl.jussieu.fr/IGCMG/Outils/ferret/Atlas392 * The atlas is a result of the post processing, which will creates a collection of plots presented as a web tree. Each plot is available as image and pdf file. The plots are made with the software ferret and the FAST and ATLAS libraries. More information on ferret and on those libraries can be found here http://wiki.ipsl.jussieu.fr/IGCMG/Outils/ferret/Atlas 381 393 * Here is an example of atlas for the coupled IPSLCM5A available on dods : [http://dods.idris.fr/rpsl003/IPSLCM5A/DEVT/pdControl/BAL1210/ATLAS/SE_2000_2009/ATM/ATM.html ATM] 382 394 * There are at least 8 directories with Atlas for the coupled model. They are based on atlas_composante.cfg files. You can look at them on the file servers in the IGCM_OUT/IPSLCM5A/DEVT/pdControl/MyExp/ATLAS directories.
