Skip to content
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

MIRI CR showers not flagged for SLOWR1 data #8030

Closed
stscijgbot-jp opened this issue Oct 26, 2023 · 4 comments · Fixed by spacetelescope/stcal#237
Closed

MIRI CR showers not flagged for SLOWR1 data #8030

stscijgbot-jp opened this issue Oct 26, 2023 · 4 comments · Fixed by spacetelescope/stcal#237

Comments

@stscijgbot-jp
Copy link
Collaborator

Issue JP-3448 was created on JIRA by David Law:

Testing indicates that the MIRI CR shower flagging code works well on FASTR1 data, but does not work on SLOWR1 data.  Code reports showers found, but it does not obviously affect the resulting rate files.

I know Michael Regan is already looking at this, but filing this ticket for visibility.

@stscijgbot-jp
Copy link
Collaborator Author

Comment by Misty Cracraft on JIRA:

Has this been tested on different types of SLOWR1 data, or just MRS? I admit I didn't have SLOWR1 data in my shower testing notebook, but I can certainly add some tests.

@stscijgbot-jp
Copy link
Collaborator Author

Comment by Michael Regan on JIRA:

When I looked at the case that David used the problem was due to residual dark current. This is an effect of the variable MIRI dark current. David and I talked about it and have a method that could correct for the variable dark rate for MRS observations.

I need to do some analysis to see if that will work.

@stscijgbot-jp
Copy link
Collaborator Author

Comment by Howard Bushouse on JIRA:

Fixed by spacetelescope/stcal#237

@stscijgbot-jp
Copy link
Collaborator Author

Comment by David Law on JIRA:

Tested and confirmed working

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant