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

Dithering and nodding #60

Open
siriobelli opened this issue Apr 23, 2020 · 2 comments
Open

Dithering and nodding #60

siriobelli opened this issue Apr 23, 2020 · 2 comments

Comments

@siriobelli
Copy link

This is a very exciting project! I have a suggestion regarding dithering (sub-pixel offsets) and nodding (large offsets to improve background subtraction). It would be nice if these modes were natively supported and did not require the data to be resampled one extra time. A clean way to do this is to include the spatial offset of each frame in the rectification solution. Ideally, both wavelength calibration and spatial rectification should be 2D mappings from observed pixel coordinates (x,y) to final rectified coordinates (wavelength, actual "vertical" position on the sky in arcsec). This way the 2D spectrum needs to be resampled only once throughout the data reduction. I wrote a detailed description of this workflow here: https://ui.adsabs.harvard.edu/abs/2018MNRAS.478.2097B -- this may be useful for inspiration, particularly for near-infrared data (but the associated code won't be as useful as it was written in IDL and not in an object-oriented way).

@tepickering
Copy link
Contributor

thank you for this and for the link to the paper! we have talked about this informally in the past, but it's good to finally have an issue in place as a marker to implement this. there's a bit more infrastructure that needs to be put in place first, but this is something specreduce should definitely support.

@jehturner
Copy link
Member

jehturner commented Apr 23, 2020

This is where we're going with the spectroscopic reduction at Gemini, using gwcs. Being able to have a single resampling step (or even none) is more-or-less the point of issue #20. Thanks for the paper (can't recall off hand whether I've seen it before).

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

No branches or pull requests

3 participants