Changes between Version 90 and Version 91 of Doc/Setup

Timestamp:

11/07/19 17:02:25 (4 years ago)

Author:

acosce

Comment:

--

Doc/Setup

@@ -585 +585 @@
 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) :
 {{{
@@ -593 +591 @@
 }}}
 
-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.  
+A temporary run directory (on the scratch for Irene and Jean Zay) 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
@@ -638 +636 @@
 ## Post-processing jobs ##
 
-Jobs headers for post-processing have to be carefully checked, especially elapsed time limits. They are in libIGCM directory (xxx.job) and are adapted for IPSLCM5A with 1Y for !RebuildFrequency and !PackFrequency. Change time limits if you use larger frequencies.
+Jobs headers for post-processing have to be carefully checked, especially elapsed time limits. They are in libIGCM directory (xxx.job), they are create when you launch for the first time the command ins_job to create an experiment. Change time limits if you use larger frequencies.
 
 ----