Changes between Initial Version and Version 1 of user/flavoni/libIGCM_v3.6/list_of_possible_errors

Timestamp:

2015-10-30T22:10:08+01:00 (5 years ago)

Author:

flavoni

Comment:

—

user/flavoni/libIGCM_v3.6/list_of_possible_errors

@@ +1 @@
+== '''List of possible errors''' ==
+[[PageOutline]]
+
+ * '''To perform a second simulation after a run with !PeriodState=Fatal'''
+
+  rm Job_name/run.card;  rm Script_Output*
+
+  but do not cancel run.card.'''init''' file, if not run.card file is not re-created.
+
+  ( File run.card.init is created with ins_job script )
+
+ * '''!RebuildFromArchive=NONE'''
+
+  In MPI it is good to use Rebuild in "archive" machine, to not ovrerload calcul machine. [[BR]]  You have to put in config.card in POST Session:
+
+  !RebuildFrequency  =1Y [[BR]]  !RebuildFromArchive  =true
+
+  NOTA BENE: If you put !RebuildFrequency  =1Y and you forget to set !RebuildFromArchive  =true, it is very dangerous. NEVER DO IT!
+
+ * '''How to do a long job without exit from queue'''
+
+  You can play with Duration Experience, PeriodLenght   and PeriodNb  , elapstim_req in this way :[[BR]]  in '''  config.card'''   Duration Experience is = !DateBegin   - !DateEnd   [[BR]]  in '''  config.card'''   !PeriodLenght   is how many time you do restart files[[BR]]  in '''  Job_Name'''   !PeriodNb   is  in '''  Job_Name'''   elapstim_req is elapsed time limit
+
+        Your job is out from queue every time that is finished a PeriodNb  , so you can do :
+
+  !PeriodNb   = ( Duration Experience ) / !PeriodLenght
+
+  but be careful with elapstim_req, because this is a limit, you've to be sure that it exists a queue that can hold you.
+
+  Simona Flavoni last update:  [[Timestamp]]