config_compsets.xml: Turned on WaveWatch for B1850 and BHISTC5L40CNR compsets. Other
B1850s and BHISTs compsets have a Ws|d added to indicate which wave
model is used SWAV or DWAV. WW3(WaveWatch) is the default.
testlist_allactive.xml: Update compset aliases to match new compset names
config_pes.xml: WaveWatch has a maximum number of 120 processors it can use. So limit the
number of processors for WaveWatch to 120.
config_grids.xml: Add ww3a grid for WaveWatch model, make sure null grid is used when not using
WaveWatch
Test suite: Ran namelist tests for prealpha and prebeta on yellowstone for intel, gnu, and pgi.
Manually checked to see if WaveWatch grid was set correctly in env_build.xml
Test baseline:
Test namelist changes: B1850 and BHIST compset names changed by adding Ws|d to indicate
if SWAV or DWAV is being used.
Test status: B1850 and BHISTC5L40CNR will have answer differences since WaveWatch was
turned on for these compsets.
config_compsets.xml: Turned on WaveWatch for B1850 and BHISTC5L40CNR compsets. Other B1850s and BHISTs compsets have a Ws|d added to indicate which wave model is used SWAV or DWAV. WW3(WaveWatch) is the default. testlist_allactive.xml: Update compset aliases to match new compset names config_pes.xml: WaveWatch has a maximum number of 120 processors it can use. So limit the number of processors for WaveWatch to 120. config_grids.xml: Add ww3a grid for WaveWatch model, make sure null grid is used when not using WaveWatch
Test suite: Ran namelist tests for prealpha and prebeta on yellowstone for intel, gnu, and pgi. Manually checked to see if WaveWatch grid was set correctly in env_build.xml Test baseline: Test namelist changes: B1850 and BHIST compset names changed by adding Ws|d to indicate if SWAV or DWAV is being used. Test status: B1850 and BHISTC5L40CNR will have answer differences since WaveWatch was turned on for these compsets.
Fixes: [CIME Github issue #]
User interface changes?:
Code review: