JP-1636: Fix slit wcs issue in extract_1d apcorr #5260
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
extract_1d
was failing when trying to process NIRSpec FS or MOS data in aMultiSlitModel
when trying to compute the pixel scale (converting arcsec from ref file to pixels), because it was trying to use the WCS from the first slit instance in the model for all slits. This was giving null/NaN results for all slits other than the first. So this updates the routine to use the WCS object for the particular slit being processed. Required adding the slit name to theApCorr
base class, so that it's available for use.Fixes #5229 / JP-1636