Changes between Version 1 and Version 2 of Documentation/UserGuide/TestCaselibIGCM

Timestamp:

2023-11-30T17:04:34+01:00 (6 months ago)

Author:

jgipsl

Comment:

--

Documentation/UserGuide/TestCaselibIGCM

@@ -3 +3 @@
 Last revision: 2023/11/30, J. Ghattas
 
-We’ll now make a first test for 3 years using the experiment set up in FG_CRUJRA_HIST. This experiment is a global historical set up using the full ORCHIDEE model in offline mode. It uses the driver "orchideedriver" also called ”the new driver”. You’ll launch using the default set up.
+This is a first test for a couple of years using the experiment set up in FG_CRUJRA_HIST. This experiment FG_CRUJRA_HIST is a global historical set up using the full ORCHIDEE model in offline mode. It starts using no restart files by default (to be changed by adding a restart file from a spinup for important simulations). This setup uses the driver "orchideedriver" also called ”the new driver”.
 
 == Prepare the experiment folder and create the job ==
@@ -28 +28 @@
 ../../../libIGCM/ins_job
 }}}
+A job called Job_MyFirstTest has now been created. 
+
+== Launch the job ==
+Launch the job on the batch system:
+{{{
+sbatch Job_MyFirstTest      # At jean-zay or spirit/spiritx
+ccc_msub Job_MyFirstTest    # At irene
+qsub Job_MyFirstTest        # At obelix
+}}}
+
+You'll see in run.card the proceeding of the job. In file Script_Output_MyFirstTest.000001 you'll see all the text output from the scripts in libIGCM. 
+
+== Find output ==
+In the Script_Output_MyFirstTest.000001, look for the variable IGCM_OUT to see where the output are stored. 
+
+If SpaceName=TEST, the output will stay in this folder (which is a temporary folder at scratch). But if SpaceName=PROD or DEVT, the output will be moved to a permanent storage at irene or jean-zay. This will be done in a post-processing job launched automatically at a certain frequency or at least in the end of the simulation.