Changes between Version 75 and Version 76 of Doc/CheckDebug

Timestamp:

02/24/23 10:40:50 (16 months ago)

Author:

acosce

Comment:

--

Doc/CheckDebug

@@ -178 +178 @@
 
 # Debug #
-## Where does the problem come from ? ##
+
 
 Your problem could come from a programming error. To find it you can use the text output of the model components located in the Debug subdirectories. Your problem could be caused by the computing environment. This problem is not always easy to identify. It is therefore important to perform benchmark simulations to learn about the usual behavior of a successfully completed simulation.
 
-### The Debug directory ###
+## The Debug directory ##
 
 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. 
@@ -202 +202 @@
 [[NoteBox(tip, Your best friend is : {{{ grep -i error * ; grep -i 'e r r o r' *ocean.output }}} , 600px)]]
 
-### Programming error ###
+## Programming error ##
 Please, take the time to read and analyze modifications you have done in the code. Nobody codes perfectly.
 
-### Unknown error ###
+## Unknown error ##
 In this case, it's possible to relaunch the main job to run again the last period.
 
@@ -225 +225 @@
 
 
-### Use of RUN_DIR directory to run without libIGCM infrastructure ###
+## Use of RUN_DIR directory to run without libIGCM infrastructure ##
 
 Sometimes, that could be useful (and more effective) to have all the information of the run in the same directory : that allows you to run directly into the RUN_DIR directory, using a Job_debug to be launched. To activate this debug functionality (available from libIGCM rev 1569) :