Changes between Version 5 and Version 6 of user/gm/Namelist_framework

Timestamp:

2018-05-03T09:02:18+02:00 (6 years ago)

Author:

gm

Comment:

--

user/gm/Namelist_framework

@@ -34 +34 @@
 
 
-There is three type of namelist :  (1) "manager"  ;  (2) "associate manager"  ;  and (3) "specific".
+There is three type of namelist :  (1) "manager"  ;  (2) "associate manager"  ;  and (3) "specific" (may be called "self-contained" or autonomous" namelist ?).
      (1) "manager" namelist : it is required in all user configuration. It defines key parameters and activate through a logical the reading of the "associate manager" namelists. By default, all choices are deactivated, while choices is required (the model will stop at the initialization phase if no choice is made) . Such a namelist is characterized by  a " (default: NO selection) " comment at the end of their opening line :
 {{{
@@ -52 +52 @@
 {{{
 !-----------------------------------------------------------------------
-&namXXX     !   sort description                                        (default: NO)
-!-----------------------------------------------------------------------
-}}}
-
-[[BR]]
-
-
-Note that two other setting of these 3 types of namelist may be adopted to add a better visual identification :
+&namXXX     !   sort description                                        (default: OFF)
+!-----------------------------------------------------------------------
+}}}
+
+[[BR]]
+
+
+Note that two other settings of these 3 types of namelist may be adopted to add a better visual identification :
 {{{
 !! manager namelist
@@ -73 +73 @@
 !! specific namelist 
 !-----------------------------------------------------------------------
-&namXXX        !   short description                                    (default: NO)
+&namXXX        !   short description                                    (default: OFF)
 !-----------------------------------------------------------------------
 }}}
@@ -89 +89 @@
 !! specific namelist 
 !-----------------------------------------------------------------------
-&namXXX        !   short description                                    (default: NO)
-!-----------------------------------------------------------------------
-}}}
-
-[[BR]]
-
-   Note also that the I'm not very found of the tags :
-      "default: NO selection" ; "ln_xxxyyy =T" ; and "default: NO"
+&namXXX        !   short description                                    (default: OFF)
+!-----------------------------------------------------------------------
+}}}
+
+[[BR]]
+
+   Note also that the I'm not very found of the tag for manager namelist :
+      "default: NO selection" 
    For example, they can be be :
-      "default: REQUIRE selection" ; "used IF ln_xxxyyy =T" ; and "default: NOT used"
+      "default: REQUIRE selection"  or "selection REQUIRED" or just "REQUIRED" ?
    or any other clever suggestion.
 
@@ -106 +106 @@
 
 === configuration namelist : ===
-This namelist aims to overwrite the reference namelist values. The way its is set in all configurations and test cases provides in the down in the NEMOGCM/CONFIG directory is the following : It have to contain the namelist :
-
-      (0) all the header of 10 sections of the ocean namelist, listing all the section namelist that are relevant for the configuration (e.g. C1D namelist description line will only appears in the C1D_PAPA configuration.
-
-      (1) In addition to namdom and namrun, ALL the "manager" namelist:  By definition all "manager namelist require to switch at least on namelist logical from FALSE to TRUE.
-
-      (2) only the "associate manager" namelist for which  the two conditions are satisfied:  -1- its manager  namelist logical equal TRUE  ; and -2- the default reference values that has been modified.
-
-      (3) only "specific" namelist for which the user have chosen to set to TRUE its control switch. In the case only the other namelist option that has been changed compare to the reference will appear.
-[[BR]]
-
-
+This namelist aims to overwrite the reference namelist values. The way it is set in all configurations and test cases (NEMOGCM/CONFIG directory) is the following : It have to contain :
+
+      (0) all the header of 10 sections of the ocean namelist, listing all the section namelist that are relevant for the configuration (e.g. C1D namelist description line will only appears in the C1D_PAPA configuration).
+
+      (1) In addition to namdom and namrun, ALL the "manager" namelist. Indeed, by definition all the "manager" namelists require to switch at least on namelist logical from FALSE to TRUE.
+
+      (2) only the "associate manager" namelist for which  the two conditions are satisfied:  -1- its manager  namelist logical equal TRUE  ; and -2- the default reference values that has been modified. 
+
+      (3) only "specific" namelist for which the user have chosen to set to TRUE its control switch.
+
+In ALL three types of namelist present in the namlist_cfg, only the namelist option that has been changed compare to the reference will appear.
+
+[[BR]]
 
 === Key changes compare to v3.6 ===
 
-- No more ORCA2 specific choices in namelist_ref.
+- No more ORCA2 specific choices in namelist_ref. Major changes:
+   namdta_tsd: ln_tsd_dmp = F ; ln_tsd_init = F
+
+   namsbc:  nn_ice = 0 (no sea-ice) ;  ln_blk = F ; ln_traqsr = F ; ln_rnf = F ; nn_fwb = 0
+
+   namrun: nn_no becomes the assimilation stage as it is now the only use of this parameter.
+
+   namtra_dmp:  ln_tradmp = F
+
+   namsbc_ssr:  nn_sssr =0
+
+   namlbc:  rn_shlat    =  -9999.  (a choice is therefore required)
+
+   namdyn_adv: ln_dynadv_vec = F
+
+   namzdf: ln_zdfevd = F
+
+   namzdf_ric: ln_mldw = F
+
+   NB: Not done but '''should be done''': nn_fsbc = 1
+
 - generalize the notion of "manager", "associate manager" and "specific" namelists
 - add the possibility of having (in the solved Primitive Equation) NO trend  in tracer or momentum advection and/or lateral mixing, Coriolis, …  
@@ -150 +171 @@
 - move ln_icebergs from namberg to namsbc namelist (affect the surface ocean boundary condition, should be a "associate manager" namelist 
 - nam_tide should it be an "associate manager" namelist ??
+- C1D: CPP key removed, C1D_PAPA moved in TEST_CASES, and ALL the three C1D namelist should be regrouped in ONE single namelist read in namusr_def namelist.
+- remove namelist control for output that are also controlled via the xIOS xml file
 [[BR]]
 
@@ -184 +207 @@
    - In logical namelist use "_OFF"  instead of "_NONE"   (e.g. ln_traldf_NONE ==> ln_traldf_OFF)   '''DONE in @9526'''
    - "specific" namelist should be called '''self-contained''' or '''autonomous''' namelist
-
-