Changes between Version 1 and Version 2 of 2013WP/2013Stream1/Configuration_Setting

Timestamp:

2012-10-19T16:05:16+02:00 (12 years ago)

Author:

gm

Comment:

--

2013WP/2013Stream1/Configuration_Setting

@@ -1 +1 @@
 = Configuration Setting =
-
-
 Last edited [[Timestamp]]
 
@@ -10 +8 @@
 Several points have to be improved regarding the management of the namelist in NEMO.
 
-  From a user point of view:[[BR]]      • global domain sizes are FORTRAN parameters, not namelist parameters[[BR]]     • 2 namelist files in each configuration (standard and agrif) with all the information
-  
+  From a user point of view:[[BR]]         • global domain sizes are FORTRAN parameters, not namelist parameters[[BR]]         • 2 namelist files in each configuration (standard and agrif) with all the variables, not only the one that depart from the default values
+  From a developer point of view:[[BR]]• the number of copies of the whole namelist (2 by configuration and an increasing number of reference configuration) make the change in namelist a nightmare [[BR]]• default values of the namelist appear twice: 1) in the namelist itself and 2) in the code, distributed in the declaration phase of numerous modules[[BR]]• global domain sizes (jpiglo, jpjglo, jpidta, jpjdta, jpkdta) are FORTRAN parameters, except in AGRIF case ==> almost as many par_XXX.h90 as the number of reference configurations ! [[BR]]• in the code old namelist variables (i.e. with a non-doctor name) still survive ==> suppression is needed.
 
-=== TITLE1.2 ===
-== TITLE2 ==
-=== TITLE2.1 ===
-=== TITLE2.2 ===
-----
+=== Proposed solution ===
+        '''I -''' global domain sizes, configuration names, etc... (all the PARAMETER in par_oce.F90) defined in the namelist. Impact: suppression of all par_XXX.h90 files. Also suppression of all key_XXX associated to configurations (key_ORCA_RXXX, key_EEL_RXXX, key_GYRE, etc...).
+
+        '''II -''' namelist:[[BR]]              • One single whole namelist by medium (ocean, ice, bio) put at CONFIG/ level in read-only mode. This namelist contains the default values. The hard coded default values spread in the modules are suppressed (together with the surviving old non-doctor variables). [[BR]]            • In each configuration the namelists of each medium contain only the sub-namelists that are changed for the configuration (the name will be namelist_cfg, name list_cfg_top, etc...). In the code, read the first the default namelist, then the configuration namelist.