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


Ignore:
Timestamp:
2018-05-03T16:11:37+02:00 (2 years ago)
Author:
nicolasmartin
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • user/gm/Namelist_framework

    v6 v7  
    1717 
    1818The ocean namelist contains 10 sections : 
    19 {{{ 
     19{{{#!f 
    2020!! NEMO/OPA  :  1 - Domain & run manager (namrun, namcfg, namdom, namtsd, namcrs, namc1d, namc1d_uvd) 
    2121!! namelists    2 - Surface boundary (namsbc, namsbc_flx, namsbc_blk, namsbc_cpl, 
     
    3636There is three type of namelist :  (1) "manager"  ;  (2) "associate manager"  ;  and (3) "specific" (may be called "self-contained" or autonomous" namelist ?). 
    3737     (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 : 
    38 {{{ 
     38{{{#!f 
    3939!----------------------------------------------------------------------- 
    4040&namXXX     !   sort description                                        (default: NO selection) 
     
    4343     
    4444     (2)  "associate manager" namelist : It is read only if its associated flag (ln_xxxyyy) appearing in its father "manager" namelist is set to true. It contains reasonable default value that user may overwrite in namelist_cfg.  Such a namelist is characterized by  a " (ln_xxxyyy =T) " comment at the end of their opening line : 
    45 {{{ 
     45{{{#!f 
    4646!----------------------------------------------------------------------- 
    4747&namXXX     !   sort description                                        (ln_xxxyyy =T) 
     
    5050 
    5151     (3) "specific" namelist : they are associated with a pure optional feature (ocean parametrization such as namtra_eiv, naltra_mle, etc.) or option that does not change the the model trajectory (diagnostics, print control, etc.).  They contains their own control switch (the first variable given in the namelist) and its default value is always FALSE. Such a type of namelist is characterized by  a " (default: NO) " comment at the end of their opening line : 
    52 {{{ 
     52{{{#!f 
    5353!----------------------------------------------------------------------- 
    5454&namXXX     !   sort description                                        (default: OFF) 
     
    6060 
    6161Note that two other settings of these 3 types of namelist may be adopted to add a better visual identification : 
    62 {{{ 
     62{{{#!f 
    6363!! manager namelist 
    6464!-==-==-==-==-==-==-==-==-==-==-==-==-==-==-==-==-==-==-==-==-==-==-==-= 
     
    7777}}} 
    7878or  
    79 {{{ 
     79{{{#!f 
    8080!-== == == == == == == == == == == == == == == == == == == == == == == = 
    8181&namXXX        !   short description                                    (default: NO selection) 
     
    152152=== things to be improved & questions : === 
    153153- move in  namsbc_wave namelist all the wave related variable that are in namsbc except ln_wave switch, that is:  
    154 {{{ 
     154{{{#!f 
    155155   ln_cdgw     = .false.   !  Neutral drag coefficient read from wave model (T => ln_wave=.true. & fill namsbc_wave) 
    156156   ln_sdw      = .false.   !  Read 2D Surf Stokes Drift & Computation of 3D stokes drift (T => ln_wave=.true. & fill namsbc_wave)