-
Notifications
You must be signed in to change notification settings - Fork 167
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
Incorrect Reference Read Noise File for NRS1 IRS2 mode #8757
Comments
Meaghan McDonald Can you check on this please? |
Comment by Meaghan McDonald on JIRA: I can confirm that jwst_nirspec_readnoise_0041.fits has both READPATT and P_READPATT keywords that are non-IRS2. The question is why is this reference file being used, and not jwst_nirspec_readnoise_0038.fits (the NRS1 equivalent to jwst_nirspec_readnoise_0042.fits in the rmap). David Law what is the observation? |
Bouncing to Michael Regan ; what was the observation number for your data? (I just spot-checked one GARDEN exposure, and it's using 0038 as expected). |
Comment by Michael Regan on JIRA: I'm sorry. I was wrong. I can't recreate where I came up with the conclusion that NRS1 IRS2 was using 0042.
|
Comment by Michael Regan on JIRA: I incorrectly used the wrong read file.
|
Issue JP-3735 was created on JIRA by Michael Regan:
When processing IRS2 mode observations, the pipeline is using the wrong reference file for the NRS1 detector on NIRSpec. The value for READPATT in the reference file header is NRSRAPID. The correct value should be NRSIRS2RAPID. The NRS1 read noise reference file used by the pipeline is:
jwst_nirspec_readnoise_0041.fits
For the same observation the NRS2 read noise reference file is:
jwst_nirspec_readnoise_0042.fits. That file has a READPATT of NRSIRS2RAPID.
This is also clearly a non-iRS2 read nose file because the read noise values are higher what I measured using recent IRS2 dark observations.
The text was updated successfully, but these errors were encountered: