Changes between Version 65 and Version 66 of Doc/CheckDebug

Timestamp:

12/01/22 16:11:05 (19 months ago)

Author:

aclsce

Comment:

--

Doc/CheckDebug

@@ -224 +224 @@
 }}}
 
+
+### Use of run_dir directory to run without libIGCM infrastructure (ongoing developments) ###
+
+Sometimes, that could be useful (and more efficious) to have all the information of the run in the same directory : that allows you the possibility to run directly inside the RUN_DIR directory, using a Job_debug to be launched. To activate this debug functionality :
+
+ * modify the main computing Job 
+{{{
+JobType=DIR 
+}}}
+
+ * go into RUN_DIR directory, as indicated in the message at the end of Script_Output of the main Job.
+
+{{{
+############################################
+#    DEBUG PHASE : CREATION OF RUN_DIR    #
+############################################
+
+You are in development or debug phase
+You can run directly into the running directory which is here
+/ccc/scratch/cont003/gencmip6/p86caub/RUN_DIR/7485895_33135/DEBUG-LIBIGCM.02.33135
+Inside the run directory you will find a Job_debug_DEBUG-LIBIGCM.02
+to be used to launch the run.
+This job stops here
+
+cd /ccc/scratch/cont003/gencmip6/p86caub/RUN_DIR/7485895_33135/DEBUG-LIBIGCM.02.33135 ; ccc_msub Job_debug_DEBUG-LIBIGCM.02
+}}}
 
 # Start or restart post processing jobs #