Changes between Version 20 and Version 21 of Doc/Running

Timestamp:

09/24/15 16:33:38 (9 years ago)

Author:

aclsce

Comment:

--

Doc/Running

@@ -93 +93 @@
 
 }}}
-## How to continue or restart a simulation ##
- 1. If you want to continue an existing or finished simulation, change the simulation end date in the `config.card` file. Do not change the simulation start date.
+
+## run.card at the end of a simulation ##
+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.
+[[BR]]This files contains the following sections :
+ * Configuration : allows you to find out how many integration steps were simulated and what would be the next integration step if the experiment would be continued. 
+{{{
+[Configuration]
+#lastPREFIX
+OldPrefix=        # ---> Prefix of the last created files during the simulation = JobName + date of the last period. Used for the Restart
+#Warning : OldPrefix not used anymore from libIGCM_v2.5.
+#Compute date of loop
+PeriodDateBegin=   #  --->start date of the next period to be simulated
+PeriodDateEnd=     # ---> end date of the next period to be simulated
+CumulPeriod=       # ---> number of already simulated periods 
+# State of Job "Start", "Running", "OnQueue", "Completed"
+PeriodState="Completed"   
+        
+SubmitPath=   # ---> Submission directory
+}}}     
+ * !PostProcessing :  returns information about the post processing status
+{{{
+[PostProcessing]
+TimeSeriesRunning=n   # ---> indicates if the timeSeries are running
+TimeSeriesCompleted=20091231   # ---> indicates the date of the last TimeSerie produced by the post processing
+}}}
+ * Log : returns technical (run-time) information such as the size of your executable and the execution time of each integration step.
+{{{
+[Log]
+# Executables Size
+LastExeSize=()
+
+#---------------------------------
+# CumulPeriod | PeriodDateBegin |   PeriodDateEnd |        RunDateBegin |          RunDateEnd |     RealCpuTime |     UserCpuTime |      SysCpuTime | ExeDate
+#           1 |        20000101 |        20000131 | 2013-02-15T16:14:15 | 2013-02-15T16:27:34 |       798.33000 |         0.37000 |         3.05000 | ATM_Feb_15_16:13-OCE_Feb_15_15:56-CPL_Feb_15_15:43
+#           2 |        20000201 |        20000228 | 2013-02-15T16:27:46 | 2013-02-15T16:39:44 |       718.16000 |         0.36000 |         3.39000 | ATM_Feb_15_16:13-OCE_Feb_15_15:56-CPL_Feb_15_15:43
+}}}
+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].
+
+## Script_Output_JobName ##
+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).
+[[BR]]
+This file contains mainly three parts : 
+ * copying and handling of input and parameters files
+ * running the model 
+ * copying of outputs files and launching of post processing steps (rebuild and pack)
+These three parts are defined as below : 
+{{{
+#######################################
+#       ANOTHER GREAT SIMULATION      #
+#######################################
+
+ 1st part (copying and handling of the input and parameter files)
+
+#######################################
+#      DIR BEFORE RUN EXECUTION       #
+#######################################
+
+ 2nd part (running the model)
+
+#######################################
+#       DIR AFTER RUN EXECUTION       #
+#######################################
+
+ 3rd part (copying of outputs files and launching of post processing steps (rebuild and pack))
+
+}}}
+
+## The output files ##
+
+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.
+
+Prior to the packs execution, this directory structure is stored 
+ * on the $SCRATCHDIR at TGCC
+ * on the $WORKDIR at IDRIS
+
+After the packs execution (see diagram below), this tree is stored
+ * on the $CCCSTOREDIR and the $CCCWORKDIR at TGCC 
+ * on the Ergon machine at IDRIS 
+
+### Here is the storage directory structure of the output files produced at TGCC ###
+
+[[Image(Resultats-TGCC.jpg, 50%)]]
+
+### Here is the storage directory structure of the output files produced at IDRIS ###
+
+[[Image(Resultats-IDRIS.jpg, 50%)]]
+
+## Debug/ directory ## 
+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].
+
+## How to continue or restart a simulation ?##
+ 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.
  1. In the `run.card` file you must: 
   * check that the `PeriodDateBegin` and `PeriodDateEnd` variables match with the next integration step of your simulation (e.g. if you just finished May 2000 and you want to integrate one month, set `PeriodDateBegin= 20000601` and `PeriodDateEnd= 2000630`) 
@@ -110 +200 @@
 ccc_msub Job_EXP00 or llsubmit Job_EXP00
 }}}
-
-## The output files ##
-
-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.
-
-Prior to the packs execution, this directory structure is stored 
- * on the $SCRATCHDIR at TGCC
- * on the $WORKDIR at IDRIS
-
-After the packs execution (see diagram below), this tree is stored
- * on the $CCCSTOREDIR and the $CCCWORKDIR at TGCC 
- * on the Ergon machine at IDRIS 
-
-### Here is the storage directory structure of the output files produced at TGCC ###
-
-[[Image(Resultats-TGCC.jpg, 50%)]]
-
-### Here is the storage directory structure of the output files produced at IDRIS ###
-
-[[Image(Resultats-IDRIS.jpg, 50%)]]
-
-## run.card at the end of a simulation ##
-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.
-[[BR]]This files contains the following sections :
- * Configuration : allows you to find out how many integration steps were simulated and what would be the next integration step if the experiment would be continued. 
-{{{
-[Configuration]
-#last PREFIX
-OldPrefix=        # ---> prefix of the last created files during the simulation = JobName + date of the last period. Used for the Restart
-#Compute date of loop
-PeriodDateBegin=   #  --->start date of the next period to be simulated
-PeriodDateEnd=     # ---> end date of the next period to be simulated
-CumulPeriod=       # ---> number of already simulated periods 
-# State of Job "Start", "Running", "OnQueue", "Completed"
-PeriodState="Completed"   
-        
-SubmitPath=   # ---> Submission directory
-}}}     
- * !PostProcessing :  returns information about the post processing status
-{{{
-[PostProcessing]
-TimeSeriesRunning=n   # ---> indicates if the timeSeries are running
-TimeSeriesCompleted=20091231   # ---> indicates the date of the last TimeSerie produced by the post processing
-}}}
- * Log : returns technical (run-time) information such as the size of your executable and the execution time of each integration step.
-{{{
-[Log]
-# Executables Size
-LastExeSize=()
-
-#---------------------------------
-# CumulPeriod | PeriodDateBegin |   PeriodDateEnd |        RunDateBegin |          RunDateEnd |     RealCpuTime |     UserCpuTime |      SysCpuTime | ExeDate
-#           1 |        20000101 |        20000131 | 2013-02-15T16:14:15 | 2013-02-15T16:27:34 |       798.33000 |         0.37000 |         3.05000 | ATM_Feb_15_16:13-OCE_Feb_15_15:56-CPL_Feb_15_15:43
-#           2 |        20000201 |        20000228 | 2013-02-15T16:27:46 | 2013-02-15T16:39:44 |       718.16000 |         0.36000 |         3.39000 | ATM_Feb_15_16:13-OCE_Feb_15_15:56-CPL_Feb_15_15:43
-}}}
-
-
-## Script_Output_JobName ##
-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).
-[[BR]]
-This file contains three parts : 
- * copying the input files
- * running the model 
- * post processing
-These three parts are defined as below : 
-{{{
-#######################################
-#       ANOTHER GREAT SIMULATION      #
-#######################################
-
- 1st part (copying the input files)
-
-#######################################
-#      DIR BEFORE RUN EXECUTION       #
-#######################################
-
- 2nd part (running the model)
-
-#######################################
-#       DIR AFTER RUN EXECUTION       #
-#######################################
-
- 3rd part (post processing)
-
-}}}
-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].
-
-
-## Debug/ directory ## 
-A Debug/ directory is created if the simulation crashed. This directory will contain 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].
 
 ----