Changes between Version 3 and Version 4 of Doc/Setup/Ensemble

Timestamp:

10/10/19 15:34:42 (5 years ago)

Author:

flavoni

Comment:

--

Doc/Setup/Ensemble

@@ -30 +30 @@
 Two type of esemble are allowed with this template:
 
-1. Ens_DATE  : creation of ensemble members, NON-Periodic, starting at some dates
-
-2. Ens_PERTURB : creation of ensemble members, PERIODIC, (and it id possible to create different initial state perturbing Sea Surface Temperature with a with noise
+Date restart ensemble which allows to configure simulations starting from different restart dates.
+-       Perturb ensemble which .
+
+
+1. Ens_DATE  : allows to configure simulations starting from different restart dates, NON-Periodic.
+
+2. Ens_PERTURB : allows to configure simulations of differents members from an initial condition which is perturbed, PERIODIC, (it is possible to create different initial state perturbing Sea Surface Temperature with a with noise)
 
 All parameters for ensemble description are in [#Ensemble.card ensemble.card] and in  [#Config.card config.card].
@@ -60 +64 @@
 The variables !DateBegin and !DateEnd will be overidden by variables present in [#Ensemble.card ensemble.card].
 {{{
+#
+# This is config.card file for IPSLCM6 configuration
+#
+#========================================================================
+#D-- Compatibility -
+[Compatibility]
+libIGCM=1.0
 #D-- UserChoices -
 [UserChoices]
-#============================
+#===========================
 JobName=CM619-LR-dcppA-hindcast
 #----- Short Name of Experiment
@@ -76 +87 @@
 #============================
 #-- leap, noleap, 360d
-CalendarType=noleap
+CalendarType=leap
 #-- Experiment dates : Beginning and ending
 #-- "YYYY-MM-DD"
@@ -82 +93 @@
 DateEnd=1980-12-31
 #============================
+ORCA_version=eORCA1.2
+#============================
 #-- 1Y, 1M, 5D, 1D Period Length of one trunk of simulation
 PeriodLength=1Y
@@ -88 +101 @@
 A section `[Ensemble]` should also be present. It contains the information that we want to prepare an ensemble simulation with variable !EnsembleRun set to y and three unset fields to be filled in the ''config.card'' of each member after ''''`ins_job -e`''' has run.
 {{{
+#===========================
 [Ensemble]
 #D- Ensemble run ? 'y' or 'n'
@@ -95 +109 @@
 EnsembleDate=
 EnsembleType=
+#
 }}}
 
 ## Ensemble.card ##
-
-There are several sections in ''ensemble.card'':
-`[Ens_PARAMETRIC]`, `[Ens_DATE]` and `[Ens_PERTURB]`.
-
-The choice of ensemble types is done by setting the variable `active` to ''y'' or ''n''.
+It is possile to choice between 2 type of esnembles in ''ensemble.card'':
+Date restart ensemble which allows to configure simulations starting from different restart dates: need to fill section `[Ens_DATE]`
+Perturb ensemble which allows to generate members from an initial condition which is perturbed by different means: need to fill section`[Ens_PERTURB]`
+
+The choice between 2 type of ensembles set the variable `active` to ''y'' of section tat you want activate: 
+To activate Date Restart non-Periodic Ensembles:
+{{{
+[Ens_DATE]
+active=y
+}}}
+
+To activate Perturbed Restart Periodic Ensembles:
+'''NOTE :''' that Period can be also just 1Y (to run non-periodic perturbed ensembles)
 {{{
 [Ens_PERTURB]
-# active=y to use this ensemble type
 active=y
 }}}
 
-There are 3 types of ensembles :
--       Parametric ensemble which is not implemented yet.
--       Date restart ensemble which allows to configure simulations starting from different restart dates.
--       Perturb ensemble which allows to generate members from an initial condition which is perturbed by different means.
 
 ## Configure a Date Restart ensemble ##