Safeguard to prevent NaNs from CRTM affecting minimisation#924
Conversation
This reverts commit d38c927.
|
At @emilyhcliu 's request, added some more info when a NaN is trapped: |
RussTreadon-NOAA
left a comment
There was a problem hiding this comment.
Looks good. One minor suggestion for this PR and PR #925.
|
WCOSS2 ctests Install All tests Passed. |
CatherineThomas-NOAA
left a comment
There was a problem hiding this comment.
@ADCollard @RussTreadon-NOAA - Hm, this is interesting. I agree that the differences are very very small. I wouldn't expect any differences at all if there weren't any NaNs captured, which when looking at the stdout for this pr, I don't see any WARNING for this new QC in the output. We're likely dealing with reproducibility in general with some more recent updates. That shouldn't impact this PR though.
The code looks good to me. Approve.
Description
As noted in #916, the CRTM can occasionally produce NaNs in the output brightness temperature and Jacobians. The existing QC tests do not always get triggered by this and so an explicit test for NaNs is required.
Type of change
Please delete options that are not relevant.
How Has This Been Tested?
Standalone runs to ensure that cases with NaNs in the CRTM brightness temperature are screened out.
Checklist