-
Notifications
You must be signed in to change notification settings - Fork 43
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Update NIRSpec anomaly flags #1410
Comments
Comment by Bryan Hilbert on JIRA: Some questions came to mind as I began making these changes (in PR #1418):
|
Comment by Bryan Hilbert on JIRA: I've reached out to the NIRISS team about the two questions above. From a NIRCam perspective I think we would be fine with applying these changes to NIRCam as well as NIRSpec. If NIRISS is on board as well, that could help simplify things. |
Comment by Bryan Hilbert on JIRA: NIRISS agrees that changing the names of the anomalies above is fine. NIRCam agrees as well. So I think it's safe to do this renaming for all NIR instruments, which will keep them all consistent. |
Comment by Bradley Sappington on JIRA: Renaming will be for all instruments. |
Comment by Bradley Sappington on JIRA: conversation with Bryan Hilbert :
|
Comment by Bradley Sappington on JIRA: |
Issue JWQL-155 was created on JIRA by Melanie Clarke:
NIRSpec would like to update the anomaly categories currently available, to better reflect which artifacts we’ve found useful to monitor.
The current categories are:
We’d like to update them to:
With this mapping:
The text was updated successfully, but these errors were encountered: