Changeset 3495 for trunk/LMDZ.COMMON/libf/evolution/deftank/README

Timestamp:

Nov 7, 2024, 10:27:18 AM (2 weeks ago)

Author:

jbclement

Message:

PEM:
Modifications related to the launching script:

• There is actually no launching difference between the 1D and 3D models. It is more about how and where you want to execute. So now, the user can choose between two launching modes with the parameter "mode" (0 = "processing scripts"; any other values = "submitting jobs"). The former option is usually used to process the script on a local machine while the latter is used to submit jobs on supercomputer;
• The execution command line in the job scripts that should be modified by the user according to the set-up is now given as an argument at the beginning to be more identifiable and adaptable;
• Making the job scripts more robust to detect a successful end.

JBC

File:

• trunk/LMDZ.COMMON/libf/evolution/deftank/README (modified) (2 diffs)

trunk/LMDZ.COMMON/libf/evolution/deftank/README

@@ -7 +7 @@
       (ii)  nPCM_ini -> the number of initial PCM runs (at least 2);
       (iii) nPCM -> the number of PCM runs between each PEM run (usually 2);
-      (iv)  dim -> the dimension of the model (1 for 1D, any other values stand for 3D).
+      (iv)  mode -> the launching mode (0 = "processing scripts"; any other values = "submitting jobs"). The former option is usually used to process the script on a local machine while the latter is used to submit jobs on supercomputer.
   The script can take an argument:
       - If there is no argument, then the script initiates a PEM simulation from scratch.
       - If the argument is 're', then the script relaunches an existing PEM simulation. It will ask for parameters to know the starting point that you want to. 
-  The script works only with the job scheduler SLURM to submit chained jobs.
+  To submit chained jobs, the script works with the job schedulers SLURM and PBS/TORQUE.
 
 # liblaunchPEM.sh:
@@ -17 +17 @@
 
 # PCMrun.job:
-  Bash script file to submit a PCM job (with SLURM or PBS/TORQUE). The name of the PCM executable file should be adapted. The headers correspond to the ADASTRA supercomputer and should be changed for other machines and job schedulers. In case of 1D, the headers are naturally omitted.
+  Bash script file to submit a PCM job (with SLURM or PBS/TORQUE). The headers correspond to the ADASTRA supercomputer and should be changed for other machines and job schedulers. In case of "processiong scripts" launching mode, the headers are naturally omitted.
   The path to source the arch file should be adapted to the machine.
-  The execution line should also be adapted according to the set-up.
+  The name of the PCM executable file should be adapted.
+  The execution command should also be adapted according to the set-up.
 
 # PEMrun.job:
-  Bash script file to submit PEM job (with SLURM or PBS/TORQUE). The name of the PEM executable file and Reshaping executable file should be adapted. The headers correspond to the ADASTRA supercomputer and should be changed for other machines and job schedulers. In case of 1D, the headers are naturally omitted.
+  Bash script file to submit PEM job (with SLURM or PBS/TORQUE).The headers correspond to the ADASTRA supercomputer and should be changed for other machines and job schedulers. In case of "processiong scripts" launching mode, the headers are naturally omitted.
   The path to source the arch file should be adapted to the machine.
-  The execution line should also be adapted according to the set-up.
-  The PEM executable can have an optional argument to specify the SLURM job ID in order to detect the job time limit and deal with it.
+  The name of the PEM executable file and Reshaping executable file should be adapted.
+  The PEM executable can have an optional argument which should be specified according to the set-up. This the job ID to make the PEM detect the job time limit.
 
 # run_PEM.def