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
Analysis of an unrelated issue has revealed that snowball flagging in build 11.1 (1.16.1) has regressed compared to build 11.0 (1.15.1). For some NIRCam data, the outer halos of snowballs is no longer removed by the snowball routine. See, e.g., jw01345001001_10201_00001_nrca3
On investigation, the root issue seems to be that the groups in which saturation is reached (but is not obvious) because of group averaging are fundamentally different from groups in which the saturation is obvious. Just like the group averaging dilutes how obvious saturation is, it also dilutes the evidence for a snowball surrounding the core. With how the snowball code is designed, when it doesn't see such evidence for a snowball in the first group in which saturation occurs it seems to not try to find and flag one.
It may be possible to address this with an update to the snowball code, but a safer alternative may be to modify the saturation code to set DO_NOT_USE instead of SATURATION for those cases in which saturation is technically reached in the individual frames but not obvious in grouped data.
Now tested on the original suite of test cases for JP-3593 and some new test cases where CR shower flagging was having some problems. All look successful, with no CR shower issues any longer but still flagging bad pixels as intended.
Issue JP-3805 was created on JIRA by David Law:
Analysis of an unrelated issue has revealed that snowball flagging in build 11.1 (1.16.1) has regressed compared to build 11.0 (1.15.1). For some NIRCam data, the outer halos of snowballs is no longer removed by the snowball routine. See, e.g., jw01345001001_10201_00001_nrca3
Initial analysis points to this being caused by https://jira.stsci.edu/browse/JP-3593, as setting saturation.use_readpatt=False fixes the issue.
The text was updated successfully, but these errors were encountered: