Changes between Version 21 and Version 22 of Doc/Running
- Timestamp:
- 09/24/15 17:30:33 (9 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Doc/Running
v21 v22 8 8 [[TOC(heading=Table of contents,depth=1,inline)]] 9 9 [[PageOutline(1,Table of contents,pullout)]] 10 10 11 ---- 11 12 12 # Submitting your simulation # 13 # Diagram of the jobs executed by the IPSL running environement # 14 The job automatically runs post processing jobs during the simulation and at different frequencies. There are two kinds of post processing: required post processing such as ''rebuild'' and ''pack'', and optional post processing such as ''!TimeSeries' and ''!SEasonal means''. 15 [[BR]] 16 Here is a diagram describing the job sequence. 17 18 [[Image(chaine.jpg, 50%)]] 19 20 # Simulation - Computing part # 21 ## Submitting your simulation ## 13 22 Once you have [wiki:DocEsetup defined and setup your simulation] you can submit it. The run scripts are: 14 23 * '''`ccc_msub`''' at TGCC … … 29 38 30 39 ---- 31 # Status of the running simulation#32 ## run.card during the simulation##40 ## Status of the running simulation ## 41 ### run.card during the simulation ### 33 42 A ''run.card'' file is created as soon as your simulation starts. It contains information about your simulation, in particular the !PeriodState parameter which is: 34 43 * `Start` or `!OnQueue` if your simulation is queued … … 37 46 * `Fatal` if your simulation was aborted due to a fatal error 38 47 39 ## Execution directory##48 ### Execution directory ### 40 49 * At TGCC your simulation is performed in a $SCRATCHDIR/RUN_DIR/job_number directory. You can check the status of your simulation in this directory. 41 50 * [[Span(id=run_dir_path)]]At IDRIS your simulation is performed in a temporary directory. You must first specify '''RUN_DIR_PATH=$WORKDIR''' in your production job if you want to monitor it. 42 51 43 ## Accounting mail##52 ### Accounting mail ### 44 53 You receive a mail « Simulation Accounting » that indicates the simulation starts fine, how many !periodNb you can use to be efficient and how many computing hours the simulation will consume. For example : 45 54 {{{ … … 56 65 57 66 ---- 58 # End of the simulation#59 60 ## messages received##67 ## End of the simulation ## 68 69 ### messages received ### 61 70 62 71 === Example of message for a successfully completed simulation === … … 94 103 }}} 95 104 96 ## run.card at the end of a simulation##105 ### run.card at the end of a simulation ### 97 106 At the end of your simulation, the !PeriodState parameter of the ''run.card'' files indicates if the simulation has been '''completed''' or was aborted due to a '''Fatal''' error. 98 107 [[BR]]This files contains the following sections : … … 131 140 If the [#run.cardattheendofasimulation run.card] file indicates a problem at the end of the simulation, you can check your Script_Output file for more details. See [wiki:DocGmonitor more details here]. 132 141 133 ## Script_Output_JobName##142 ### Script_Output_JobName ### 134 143 A Script_Output_JobName file is created for each job executed. It contains the simulation job output log (list of the executed scripts, management of the I/O scripts). 135 144 [[BR]] … … 160 169 }}} 161 170 162 ## The output files##171 ### The output files ### 163 172 164 173 The output files are stored on file servers. Their name follows a standardized nomenclature: IGCM_OUT/!TagName/[!SpaceName]/[!ExperimentName]/!JobName/ in different subdirectories for each "Output" and "Analyse" component (e.g. ATM/Output, ATM/Analyse), DEBUG, RESTART, ATLAS and MONITORING. … … 172 181 * on the Ergon machine at IDRIS 173 182 174 ### Here is the storage directory structure of the output files produced at TGCC###183 #### Here is the storage directory structure of the output files produced at TGCC #### 175 184 176 185 [[Image(Resultats-TGCC.jpg, 50%)]] 177 186 178 ### Here is the storage directory structure of the output files produced at IDRIS###187 #### Here is the storage directory structure of the output files produced at IDRIS #### 179 188 180 189 [[Image(Resultats-IDRIS.jpg, 50%)]] 181 190 182 ## Debug/ directory##191 ### Debug/ directory ### 183 192 A Debug/ directory is created if the simulation crashed. This directory contains text files from each of the model components to help you finding reasons for the crash. See also [wiki:DocGmonitor#Debug the chapter on monitoring and debugging]. 184 193 185 ## How to continue or restart a simulation ?##194 ### How to continue or restart a simulation ?### 186 195 1. If you want to continue an existing and finished simulation, change the simulation end date in the `config.card` file. Do not change the simulation start date. 187 196 1. In the `run.card` file you must: … … 202 211 203 212 ---- 204 # Simplified diagram of the jobs executed by the IPSL models and tools # 205 The job automatically runs post processing jobs during the simulation and at different frequencies. There are two kinds of post processing: required post processing such as ''rebuild'' and ''pack'', and optional post processing such as ''!TimeSeries' and ''!SEasonal means''. 206 [[BR]] 207 Here is a diagram describing the job sequence. 208 209 [[Image(chaine.jpg, 50%)]] 210 211 # Post processing with libIGCM # 212 213 214 # Simulation - Post processing and diagram part # 213 215 ## Post processing in config.card ## 214 216 You must specify in ''config.card'' the kind and frequency of the post processing. … … 396 398 * dods at IDRIS: http://dodsp.idris.fr 397 399 398 # How to check that the post processing was successful#400 ## How to check that the post processing was successful ## 399 401 400 402 The post processing output log files are :
