Changes between Version 44 and Version 45 of Doc/CheckDebug
- Timestamp:
- 10/10/19 12:56:52 (4 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Doc/CheckDebug
v44 v45 69 69 * The first line returns the job name and the date of the last time data saved to disk in the `run.card`. 70 70 * `DateBegin` - !DateEnd : start and end dates of the simulation as defined in `config.card`. 71 * !PeriodState: variable coming from the `run.card` giving the run's status :72 * !OnQueue, Waiting: the run is queued ;73 * Running: the job is running ;74 * Completed: the run was completed successfully ;75 * Fatal: the run failed.76 * Current Period : this variable from `run.card` shows which integration step (most often which month) is being computed77 * !CumulPeriod: variable from `run.card`. Number of the period being computed78 * Pending Rebuilds, Nb | From | To : number of files waiting to be "rebuild", date of the oldest and the latest files.71 * `PeriodState` : variable coming from the `run.card` giving the run's status : 72 * `OnQueue`, `Waiting` : the run is queued ; 73 * `Running` : the job is running ; 74 * `Completed` : the run was completed successfully ; 75 * `Fatal` : the run failed. 76 * `Current Period` : this variable from `run.card` shows which integration step (most often one month or one year) is being computed 77 * `CumulPeriod` : variable from `run.card`. Number of the period being computed 78 * `Pending Rebuilds, Nb | From | To` : number of files waiting to be "rebuild", date of the oldest and the latest files. Most of the configuration use parallel I/O and have not more rebuild steps. 79 79 1. The third block contains the status of the latest post processing jobs, the Rebuilds, the Pack, the Monitoring and the Atlas. Only the computed periods are returned for the Monitoring and the Atlas. For the other processing jobs, the computed periods and the number of successfully transferred files are returned. 80 80 1. Lastly, the current date. … … 114 114 * `Script_Output_JobName` 115 115 116 A `Debug/` directory is created if the simulation failed. This directory contains diagnostic text files for each model component. 116 A `Debug/` directory is created if the simulation failed in a way that is correctly diagnosed by libIGCM. This directory contains diagnostic text files for each model component. It won't be created if the job reaches the time limit and is stopped by the batch scheduler. 117 118 If the crash is not properly handeld by ligIGCM, you will find a lot of files in $RUN_DIR. In `Script_Output_JobName`, find the line starting with `IGCM_sys_Cd : ` and get the location of the RUN_DIR. 117 119 118 120 If the simulation was successfully completed output files will be stored in the following directory: … … 242 244 If the simulation failed due to abnormal exit from the executable, a Debug/ directory is created in the working directory. It contains output text files of all model components for your configuration. You should read them to look for errors. For example : 243 245 244 * xxx_out_gcm.e_error--> lmdz text output245 * xxx_out_orchidee--> orchidee text output246 * xxx_ocean.output--> nemo text output247 * xxx_inca.out--> inca text output248 * xxx_run.def--> lmdz parameter files249 * xxx_gcm.def--> lmdz parameter files250 * xxx_traceur.def--> lmdz parameter files251 * xxx_physiq.def--> lmdz parameter files252 * xxx_orchidee.def--> orchidee parameter files246 * `xxx_out_gcm.e_error` --> lmdz text output 247 * `xxx_out_orchidee` --> orchidee text output 248 * `xxx_ocean.output` --> nemo text output 249 * `xxx_inca.out` --> inca text output 250 * `xxx_run.def` --> lmdz parameter files 251 * `xxx_gcm.def` --> lmdz parameter files 252 * `xxx_traceur.def` --> lmdz parameter files 253 * `xxx_physiq.def` --> lmdz parameter files 254 * `xxx_orchidee.def` --> orchidee parameter files 253 255 254 256 [[NoteBox(tip, Your best friend is : {{{ grep -i error * ; grep -i 'e r r o r' *ocean.output }}} , 600px)]] … … 276 278 }}} 277 279 278 ## On CURIE: How to use the ddt debugger for the coupled model (or any other MPMD mode) ##279 Read this [wiki:Doc BenvBtgccAcurie#HowtousetheddtdebuggerforthecoupledmodeloranyotherMPMDmode page]280 281 ## Debug on Curie ##282 Read this [wiki:Doc BenvBtgccAcurie#Errorsoncuriewhenrunningsimulations page]280 ## On Irene : How to use the ddt debugger for the coupled model (or any other MPMD mode) ## 281 Read this [wiki:Doc/Env/TgccIrene#HowtousetheddtdebuggerforthecoupledmodeloranyotherMPMDmode page] 282 283 ## Debug on Irene ## 284 Read this [wiki:Doc/Env/TgccIrene#Errorsoncuriewhenrunningsimulations page] 283 285 284 286 … … 365 367 libIGCM=${libIGCM:=::modipsl::/libIGCM} # path of the libIGCM library 366 368 367 MASTER=${MASTER:= curie|ada} # machine on which you work369 MASTER=${MASTER:=irene|jeanzay} # machine on which you work 368 370 369 371 DateBegin=${DateBegin:=20000101} # start date of the period to be packed … … 391 393 libIGCM=${libIGCM:=::modipsl::/libIGCM} # path of the libIGCM library 392 394 393 MASTER=${MASTER:= curie|ada} # machine on which you work395 MASTER=${MASTER:=irene|jeanzay} # machine on which you work 394 396 395 397 DateBegin=${DateBegin:=20000101} # start date of the period to be packed