Safeguard to prevent NaNs from CRTM affecting minimisation#925
Conversation
RussTreadon-NOAA
left a comment
There was a problem hiding this comment.
Looks good. See comment in PR #294. Same comment applied to this PR.
Good idea! Change pushed. |
|
WCOSS2 ctests Install The four failed tests are due to non-reproducible results between the updat and contrl. For each case the initial total penalities are identical between updat and contrl. Differences arise in the minimization. rrfs_3denvar_rdasens hafs_3denvar_hybens hafs_4denvar_glbens_ global_4denvar_ Interestingly, Cactus ctests all Passed for PR #924. |
|
Ursa ctests Install This result differs from WCOSS2 (Cactus). The Cactus and Ursa builds use different versions of the Intel fortran compiler.
Also, Cactus uses hpc-stack for libraries and modules. Ursa uses spack-stack/1.9.2. |
|
@CatherineThomas-NOAA After discussion with @RussTreadon-NOAA , we are leaning towards allowing this change to proceed despite the small minimization differences. Do you concur? |
CatherineThomas-NOAA
left a comment
There was a problem hiding this comment.
Same comment from #924 apply here as well
|
**Gaea C6 ctests` Install All tests _Passed. The Gaea C6 build uses |
|
WCSOSS2 tests Test 1 Run
Below is a comparison of the minimum and maximum differences in the The maximum absolute difference between the analysis increments from the two executables is very small. Test 2
The |
Description
As noted in Issue #916 and also in PR #924 (the equivalent merge into the
develop-v16release branch), 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