Changes between Version 4 and Version 5 of 2013WP/2013Stream1/Configuration_Setting

Timestamp:

2012-12-05T06:52:22+01:00 (11 years ago)

Author:

gm

Comment:

--

2013WP/2013Stream1/Configuration_Setting

@@ -10 +10 @@
 From a user point of view:
 
-  • global domain sizes are FORTRAN parameters, not namelist parameters[[BR]]  • a namelist file in each configuration with all the variables (i.e. all the sub-namelist), not only the sub-namelist that depart from the default values
+  • global domain sizes are FORTRAN parameters, not namelist parameters[[BR]]     • a namelist file in each configuration with all the variables (i.e. all the sub-namelist), not only the sub-namelist that depart from the default values
 
 From a developer point of view:
 
-  • 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.
+  • 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.
 
 == [[BR]]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...).
+  '''          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 by medium (ocean, ice, top, ...: '''namelist_ref''', namelist_ice_ref, name list_top_ref, ...) 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 changes associated with the configuration (the name may be '''namelist_cfg''', namelist_cfg_top, etc...). A pearl script will be used to build the all the namelists that are required to run NEMO:   [[BR]]        '''namelist'''          '''= namlist_ref                + namelist_cfg   changes [[BR]]'''      namelist_top    = namlist_top_ref       + namelist_top_cfg changes [[BR]]       etc ...
-    ''''''
-''''''
+  '''          II -'''           namelist:[[BR]]                          • One single whole by medium (ocean, ice, top, ...: '''   namelist_ref'''   , namelist_ice_ref, name list_top_ref, ...) 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 changes associated with the configuration (the name may be '''   namelist_cfg'''   , namelist_cfg_top, etc...). A pearl script will be used to build the all the namelists that are required to run NEMO:   [[BR]]
+
+    namelist == namlist_ref       + namelist_cfg        changes[[BR]]namelist_top == namlist_top_ref + namelist_top_cfg changes[[BR]]etc ...