Changes between Version 68 and Version 69 of Doc/Setup

Timestamp:

10/11/19 15:51:24 (5 years ago)

Author:

falletti

Comment:

--

Doc/Setup

@@ -443 +443 @@
 $CCCSTOREDIR/IGCM_OUT/!TagName/[!SpaceName]/[!ExperimentName]/!JobName/DEBUG
  * IDRIS : 
-$ARCHIVE/IGCM_OUT/!TagName/[!SpaceName]/[!ExperimentName]/!JobName/DEBUG
+$STORE/IGCM_OUT/!TagName/[!SpaceName]/[!ExperimentName]/!JobName/DEBUG
 
 ### The [!OutputFiles] section ###
@@ -503 +503 @@
 #!sh
 RestartPath=/u/rech/lab/plabxxx/IGCM_OUT/IPSLCM5A/DEVT/pdControl 
-# or RestartPath=/dmnfs/contxxx/login/IGCM_OUT/IPSLCM5A/DEVT/pdControl
 }}}
 [[BR]]
@@ -550 +549 @@
 # Main job of the simulation #
 
-The main job contains scripts that will be executed by the system. With libIGCM, this job is unique (in the beginning AA_job and later Job_MYJOBNAME) for all type of configurations. It contains all scripts to initialize a simulation, to summarize the chosen model configuration and to run identical experiments for all model components. It resubmits itself in order to continue the simulation if needed.
-
-The job header depends on the machine type. It contains the job name and the parameters. '''Real-times''' must be chosen to match the specific classes for the computing machine and according to the simulation length (test or production).
+The main job contains scripts that will be executed by the system. With libIGCM, this job is unique (with the name '''`Job_MYJOBNAME`''') for all type of configurations. It contains all scripts to initialize a simulation, to summarize the chosen model configuration and to run identical experiments for all model components. It resubmits itself in order to continue the simulation if needed.
+
+The job header depends of the machine type. It contains the job name and the parameters. 
 
 At TGCC you must specify the project number: [wiki:Doc/ComputingCenters/TGCC#Projectandcomputingneeds  #MSUB -A MY_PROJECT].
 
-You should change the !PeriodNb parameter in the job to change the number of runs in one job (see the example of computation in the next section) :
+You should change the `!PeriodNb` parameter in the job to change the number of runs in one job (see the example of computation in the next section) :
 {{{
 #D- Number of execution in one job
-PeriodNb=1
-}}}
-
-A temporary run directory will be created for the execution of the job. This directory is always removed after successful run but when the job run fails it depends on the system if the directory is kept or not. Therefore you can change the default location by setting RUN_DIR_PATH variable as you like. This is very useful for debugging at ada, obelix or ciclad. 
+PeriodNb=10
+}}}
+
+A temporary run directory will be created for the execution of the job. This directory is always removed after successful run but when the job run fails it depends on the system if the directory is kept or not. Therefore you can change the default location by setting RUN_DIR_PATH variable as you like. This is very useful for debugging.  
 {{{
 #D- Define running directory
@@ -569 +568 @@
 }}}
 
-Here is the diagram of the steps in AA_job :
+Here is the diagram of the steps in the template script (''AA_job'') that will be use to create the job file:
 
 [[Image(AA_job.jpg, 50%)]]
@@ -593 +592 @@
 {{{
 #!sh
-cd modipsl/config/LMDZOR_v5
-cp -r DIADEME CHOUCROUTE
+cd modipsl/config/LMDZOR_v6
+cp -r MyJobTest CHOUCROUTE
 cd CHOUCROUTE
-rm -f Job_DIADEME run.card Script_Output_DIADEME.000001 
+rm -f Job_MyJobTest run.card Script_Output_MyJobTest.000001 
 vi config.card
    JobName=CHOUCROUTE