Changes between Version 54 and Version 55 of Doc/CheckDebug

Timestamp:

11/08/19 10:34:44 (5 years ago)

Author:

acosce

Comment:

--

Doc/CheckDebug

@@ -99 +99 @@
 # Analyzing the Job output : Script_Output #
 Reminder --> This file contains three parts: 
- * copying the input files
+ * prepare parameters files, and copying the input files
  * running the model 
  * post processing
@@ -108 +108 @@
 #######################################
 
- 1st part (copying the input files)
+ 1st part (prepare parameters files, copying the input files)
 
 #######################################
@@ -130 +130 @@
    * you didn't specify `OnQueue`in the `run.card` file in case you wanted to continue the simulation; 
    * one of the input files was missing (e.g. it doesn't exist, the machine has a problem,...); 
-   * the frequencies (`RebuildFrequency`, `PackFrequency` ...) do not match `PeriodLength`.
+   * the frequencies (`PackFrequency` ...) do not match `PeriodLength`.
+   * `PeriodLength` do not match with `DateBegin` and `DateEnd`
 
  * if the file ends in the middle of the second part, it's most likely because you didn't request enough memory or CPU time.
@@ -142 +143 @@
 {{{
 ========================================================================
-EXECUTION of : mpirun -f ./run_file > out_run_file 2>&1
+EXECUTION of : /usr/bin/time ccc_mprun -E-K1  -f ./run_file
 Return code of executable : 1
 IGCM_debug_Exit :  EXECUTABLE
+
+!!!!!!!!!!!!!!!!!!!!!!!!!!
+!!   ERROR TRIGGERED    !!
+!!   EXIT FLAG SET      !!
+!------------------------!
+
+0 - IGCM_debug_Exit (_0_)
+IGCM_sys_Mkdir : /path_of_your_simulation/Debug
+IGCM_sys_Cp : out_execution /path_of_your_simulation/Debug/JobName_PeriodDateBegin_PeriodDateEnd_out_execution_error
+========================================================================
+
+}}}
+If the following message is displayed :
+{{{
+========================================================================
+EXECUTION of : mpirun -f ./run_file > out_run_file 2>&1
+========================================================================
+}}}
+
+If there is a message indicating that the `restartphy.n` file doesn't exist it means that the model simulation was completed but before the end date of your simulation. If this happens you must refer to the output log of each model of your simulation.
+For example, the output file of the ocean model is stored on the file server under this name:
+{{{
+IGCM_sys_Put_Out : ocean.output xxxxxxxx/OCE/Debug/xxxxxxxx_ocean.output
+}}}
+you can retrieve them in the RUN_DIR directory of your simulation.
+
+[[NoteBox(tip,In general\, if your simulation stops you can look for the keyword "IGCM_debug_CallStack" in this file. This keyword will come after a line explaining the error you are experiencing., 600px)]]
+{{{
+Example : 
+
+--Debug1--> IGCM_comp_Update
+
+IGCM_debug_Exit :  IGCM_comp_Update missing executable create_etat0_limit.e
 
 !!!!!!!!!!!!!!!!!!!!!!!!!!
 !! IGCM_debug_CallStack !!
 !------------------------!
-
-!------------------------!
-IGCM_sys_Cp : out_run_file xxxxxxxxxxxx_out_run_file_error
-========================================================================
-}}}
-If the following message is displayed :
-{{{
-========================================================================
-EXECUTION of : mpirun -f ./run_file > out_run_file 2>&1
-========================================================================
-}}}
-
-If there is a message indicating that the `restartphy.n`" file doesn't exist it means that the model simulation was completed but before the end date of your simulation. If this happens and if your model creates an output log other than the simulation output log, you must refer to this log.
-For example, the output file of the ocean model is stored on the file server under this name:
-{{{
-IGCM_sys_Put_Out : ocean.output xxxxxxxx/OCE/Debug/xxxxxxxx_ocean.output
-}}}
-For LMDZ your output log is the same as the simulation output log and it has not been copied to the storage space. If your simulation has been performed on $SCRATCHDIR (TGCC) you can retrieve it there. Otherwise, you must restart your simulation using $WORKDIR (IDRIS) as the working directory keeping all needed files. You must also change the RUN_DIR_PATH variable. See [#run_dir_path here] before restarting it.
-
-
-[[NoteBox(tip,In general\, if your simulation stops you can look for the keyword "IGCM_debug_CallStack" in this file. This keyword will come after a line explaining the error you are experiencing., 600px)]]
-{{{
-Example : 
-
---Debug1--> IGCM_comp_Update
-
-IGCM_debug_Exit :  IGCM_comp_Update missing executable create_etat0_limit.e
-
-!!!!!!!!!!!!!!!!!!!!!!!!!!
-!! IGCM_debug_CallStack !!
-!------------------------!
 }}}
 
@@ -191 +194 @@
 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 :
 
- * `xxx_out_gcm.e_error` --> lmdz  text output
+ * `xxx_out_gcm.e.err` and `xxx_out_gcm.e.out`(or `xxx_out_lmdz.e.err` and `xxx_out_lmdz.e.out`) --> lmdz  text output 
  * `xxx_out_orchidee` --> orchidee text output 
  * `xxx_ocean.output` --> nemo text output
@@ -224 +227 @@
 # CCYY = year up to which you are deleting everything (this year included). By default, it's the current year in run.card
 }}}
-
-## On Irene : How to use the ddt debugger for the coupled model (or any other MPMD mode)  ##
-
-## Debug on Irene ##