CCPP physics: wet() bug fix and workaround for bad tsfco #916
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
Fixes this problem:
It was caused by missing values (-1e+20) for sea surface temperature on
wet
points in input data. (Wet
points are points where the CCPPwet
array is true, thus indicating the surface is at least partly water.) There's a bug fix and a workaround:wet
array can be mistakenly true when it should be false due to the location being 100% ice. An "else" statement corrects this.wet
point, the lowest model level temperature is used instead.There is no other temperature available on those points that can reasonably be used as a sea surface temperature. The lowest model level temperature may not be a perfect analogue for the sea surface temperature, but it'll be more realistic than -1E+20 K.
Issue(s) addressed
Testing
How were these changes tested?
What compilers / HPCs was it tested with?
Hera.
Are the changes covered by regression tests? (If not, why? Do new tests need to be added?)
A lower-resolution version of this configuration has a regression test.
This specific input that causes a problem is too high a resolution to be a regression test. Also, this problem likely originates from trouble with the initial conditions. We don't need to test the model with potentially problematic input.
Have the ufs-weather-model regression test been run? On what platform?
Hera.
Will the code updates change regression test baseline? If yes, why? Please show the baseline directory below.
No.
Dependencies
Requirements before merging