You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
build-namelist looks at all entries where every attribute matches, and then takes the value corresponding the entry with the most matches. Unlike in #15, if multiple entries match the same number of attributes, the namelist generation tool defaults to the FIRST item in the list. So in this case, if you run with the gx1v7 grid, CORE_IAF_JRA forcing, and POP in 1D mode, sfwf_weak_restore = 0.046. We want sfwf_weak_restore = 0.0 whenever running in 1D mode, regardless of forcing... so the last two lines in the block above should be swapped.
Version:
CESM: 2.1 and the 2.2 development branches
POP2: cesm2_1_x_rel and master
Note that JRA forcing is not available in CESM 2.0, so that version of the code is not affected.
Machine/Environment Description:
Discovered on cheyenne during a code review with @klindsay28 but problem should be evident on any machine
Any xml/namelist changes or SourceMods:
None
The text was updated successfully, but these errors were encountered:
mnlevy1981
changed the title
Bad xml entry in namelist_defaults_pop.xml
Bad XML entry in namelist_defaults_pop.xml
Sep 4, 2019
Description of the issue:
The following block of code in
bld/namelist_files/namelist_defaults_pop.xml
doesn't behave as expected:build-namelist
looks at all entries where every attribute matches, and then takes the value corresponding the entry with the most matches. Unlike in #15, if multiple entries match the same number of attributes, the namelist generation tool defaults to the FIRST item in the list. So in this case, if you run with thegx1v7
grid,CORE_IAF_JRA
forcing, and POP in 1D mode,sfwf_weak_restore = 0.046
. We wantsfwf_weak_restore = 0.0
whenever running in 1D mode, regardless of forcing... so the last two lines in the block above should be swapped.Version:
cesm2_1_x_rel
andmaster
Note that JRA forcing is not available in CESM 2.0, so that version of the code is not affected.
Machine/Environment Description:
Discovered on cheyenne during a code review with @klindsay28 but problem should be evident on any machine
Any xml/namelist changes or SourceMods:
None
The text was updated successfully, but these errors were encountered: