Changes between Version 60 and Version 61 of Doc/Setup

Timestamp:

10/10/19 17:17:14 (5 years ago)

Author:

falletti

Comment:

--

Doc/Setup

@@ -80 +80 @@
 [[Image(ins_job_v6.png, 800px)]] 
 
+For more details about the `ins_job` script, you can have a look at the [#Thescriptins_job following sub-section.]
+
+----
+'''To summarize to create a submission directory:''' \\ \\ 
+{{{
+cd modipsl/config/LMDZOR_v6
+cp EXPERIMENTS/LMDZOR/clim_360d/config.card . 
+vi config.card             ### Modify at least JobName=MYEXP
+../../libIGCM/ins_job      ### Answer the questions
+}}}
+----
+
 ## The script ins_job ##
-ins_job is a script with 4 purposes :
- * create a submission directory. This will only be done if ins_job is launched from a directory where EXPERIMENTS and GENERAL sub-dirctories are found
- * create a main job corresponding to a simulation. The main job is based on libIGCM/AA_job
- * create post-processing jobs in libIGCM using all other libIGCM/AA_* files
- * prepare the ensembles(optional, see section 6 in the end of this page)
-
-
-ins_job is found in libIGCM. It should be run directly from where the config.card is found: in the configuration directory or in the submission directory. Note that previous versions than libIGCM_v2.6 did not contain ins_job. ins_job was then stored in modipsl/util. ins_job will never overwrite an existing job or directory. For example the post-treatement jobs in libIGCM will only be done the first time ins_job is launched or if the jobs were deleted. The submission directory will only be created if it is not already done. The !JobName and options about parallelization (number of cores per executable) are used to create the main job.
-
-
-[[NoteBox(note, Use ../../../libIGCM/ins_job or ../../libIGCM/ins_job from the directory where the config.card is found. util/ins_job should not be used anymore., 600px)]] 
+`ins_job` is a script with 4 purposes :
+ * create a submission directory. This will only be done if `ins_job` is launched from a directory where EXPERIMENTS and GENERAL sub-directories are found;
+ * create a main job corresponding to a simulation. The main job is based on libIGCM/AA_job;
+ * create post-processing jobs in libIGCM using all other libIGCM/AA_* files;
+ * prepare the ensembles (optional, see section 6 bellow).
+
+
+The script `ins_job` should be run directly from where the config.card is found (in the configuration directory or in the submission directory). Note that `ins_job` will never overwrite an existing job or directory. [[BR]]
+The !JobName and options about parallelization (number of cores per executable) are used to create the main job header (cf [#Mainjobofthesimulation Main job of the simulation] section bellow).
 
 
@@ -99 +109 @@
 
 {{{
-#!sh 
-cd DIADEME
+cd MyJobTest
 ls 
   config.card COMP/ PARAM/ POST/ DRIVER/