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

Better fix for flux drop in substrip96 data for NIRISS SOSS extract_1d #9070

Open
stscijgbot-jp opened this issue Jan 13, 2025 · 0 comments
Open

Comments

@stscijgbot-jp
Copy link
Collaborator

Issue JP-3846 was created on JIRA by Ned Molter:

The linked ticket JP-3745 found an unphysical decrease in the flux of the output spectrum in Order 1 between 1.50 and 1.55 um when the SUBSTRIP96 subarray was used.

The problem seemed to be related to a problem with the extraction aperture for Order 2 and/or the location of the trace profile of Order 2 c.f. that aperture.

The fix provided in that ticket was to simply un-mask the entire Order 2 extraction region.  This seems to be adequate for all test cases so far, but is unsatisfying: we didn't really track down the root of the problem.

The current version may also lead to noisier or slightly incorrect extractions because it doesn't properly weight pixels that are half-in, half-out of the extraction region, and it doesn't set the weight of regions that definitely do not contain data to zero.

spacetelescope/pysiaf#362 may also be related.

Link to the lines where the original fix from JP-3745 was inserted is here

if subarray == 'SUBSTRIP96':
 

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

No branches or pull requests

1 participant