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

Nirspec IFU: Slit to MSA transform issue #1898

Closed
nden opened this issue Apr 13, 2018 · 3 comments
Closed

Nirspec IFU: Slit to MSA transform issue #1898

nden opened this issue Apr 13, 2018 · 3 comments

Comments

@nden
Copy link
Collaborator

nden commented Apr 13, 2018

The transform from slit to MSA for the IFU includes transforming slit coordinates
through the Slicer transforms, followed by the IFU-POST transforms.
Using Slity, lam supplied by ESA as inputs, the pipeline does not reproduce the MSA
positions outputs.
This issue is awaiting clarification by the IDT team.

@nden nden self-assigned this Apr 13, 2018
@nden nden added assign_wcs NIRSPEC NIRSpec IFU 🔥 High Priority/Issue actively being worked labels Apr 13, 2018
@nden nden added this to the Build 7.1.1 milestone Apr 13, 2018
@nden
Copy link
Collaborator Author

nden commented Apr 16, 2018

Update from the IDT team:

I had a look at our code to double check what we are writing out on the
extensions of the IFU traces and it is the "MSA - IFU entrance"
coordinates. I apologize if that is not clear from the extension
headers. To recap:

- in the calculation to find the trace and derive the wavelength, the
IFU calculations are done from the slicer to the direction of the FPA.
That MSA plane is what we call the *MSAout*, and the transforms to use
to go from slicer plane to MSAout are the IFU-POST[slice] (forward), as
described in my IFU note Sec. 3.1.2.

- in order to go to sky, the IFU calculations are done from the slicer
in the direction of V2V3. That MSA plane is what we call *MSAin* (where
light enters the IFU), and the transforms to use to go from slicer plane
to MSAin are the IFU-FORE^-1 (backward!), as described in my IFU note
Sec. 4.3 .

The values that we output in the Trace in the extensions called MSAx and
MSAy are the ones on the *MSAin* plane (the second example I gave
above). In your script you are calculating the MSAout. Once you have
MSAin, you are ready to go to OTEIP and then to V2V3.

On the bright side, I checked your example and if I calculate the MSAout
coordinates I get the same results as your script (machine precision
agreement!), great.

This means the code needs to be changed to remove the IFUPOST transform when going to sky.
There should be some indication that the msa_frame frame in the Nirspec IFU WCS pipeline refers to the MSA entrance (direction is from sky to detector). A description attribute can be used spacetelescope/gwcs#151

@nden
Copy link
Collaborator Author

nden commented Apr 16, 2018

@stscieisenhamer @jdavies-st The comments from the team clarify this issue.

@nden
Copy link
Collaborator Author

nden commented Apr 19, 2018

Fixed in commit d0686a86c1.

@nden nden closed this as completed Apr 19, 2018
@stscieisenhamer stscieisenhamer removed the 🔥 High Priority/Issue actively being worked label Jul 29, 2018
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

2 participants