Changes between Version 10 and Version 11 of Developers/Namelist Checker


Ignore:
Timestamp:
2020-06-08T17:04:19+02:00 (4 months ago)
Author:
acc
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • Developers/Namelist Checker

    v10 v11  
    118118 
    119119Surprisingly a few variables are flagged even for a fresh copy of r4.0-HEAD (Rev: 13029): 
    120  
     120{{{ 
     121#!html 
     122<h3 style="text-align: left; color: red; background: yellow"> 
     123 Update:sbcwave.F90 contained a namelist with a continuation line without a leading ampersand, these results are with this uncommitted fix: 
     124</h3> 
     125}}} 
    121126{{{ 
    122127python nemo_nml_check.py -r pseudo_nml_ref -c namelist_ref -m 0.75 
    123 No match in matching blocks for:                           |  Possible close match: 
    124 sn_wnum                in namsbc_wave  (at line no.  497)  |  sn_wmp 
    125 sn_tauwoc              in namsbc_wave  (at line no.  498)  | 
    126 sn_tauwx               in namsbc_wave  (at line no.  499)  | 
    127 sn_tauwy               in namsbc_wave  (at line no.  500)  | 
    128128clname(1)              in nam_tide     (at line no.  581)  |  clname 
    129129tname(1)               in nam_diaharm  (at line no. 1188)  |  tname 
     
    142142}}} 
    143143 
    144 It is probably the case that the structure variables flagged (sn_*) are false positives. This is because only the structure name is declared in the namelist but individual members of the structure may be (and are) set in the ''namelist_ref''. Nonetheless, there are  a few normal variables to investigate and this does illustrate the potential usefulness of this tool. Note, the 'possible close matches' are provided by a simple string comparator. By default, only matches exceeding a closeness factor of 0.75 are reported. More (or fewer) possibilities can be provided by decreasing (or increasing) this factor between 0 and 1. This is done by providing the additional command line argument '-m fatc' as shown here (although it was unnecessary since 0.75 is the default value). 
     144It is probably the case that the structure variables flagged (sn_*) are false positives. This is because only the structure name is declared in the namelist but individual members of the structure may be (and are) set in the ''namelist_ref''. Nonetheless, there are  a few normal variables to investigate and this does illustrate the potential usefulness of this tool. Note, the 'possible close matches' are provided by a simple string comparator. By default, only matches exceeding a closeness factor of 0.75 are reported. More (or fewer) possibilities can be provided by decreasing (or increasing) this factor between 0 and 1. This is done by providing the additional command line argument '-m fac' as shown here (although it was unnecessary since 0.75 is the default value). 
    145145 
    146146Secondly, reversing the roles of the input namelists allows a check on whether or not all the available namelist variables have a default setting in ''namelist_ref'':