-
Notifications
You must be signed in to change notification settings - Fork 0
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
Can't spatially match images with SIP #203
Comments
I see the rendered ra and dec axes are swapped. Is that supposed to be? |
Yes, but with a gigantic "?" next to that yes. JWST observes on its side, so the CD1_1/CD2_2 matrices are always rotated 90 deg. The most natural way to display the pixel coordinates is therefore with RA vertical, dec horizontal. It is confusing as heck working with 90-deg rotates WCSes, but that's what blocking out the sun does for you. |
@keflavich would it be possible to have a test FITS image for diagnostics, please? |
@kswang1029 Ok, I am going to look at whether I can obtain JWST NIRCam L2 product with |
Anything from the JWST archives on MAST should work; if you need me to, I can dig up a file |
Many thanks for your report! Please don't use level 2 JWST product with current released. CARTA but level 3 JWST product looks Ok, at least it can spatially matched well (quick check by my eyes) with MIRI-IFU and ALMA. |
Is there any chance you'll add support for SIP in a future release, and any idea on the timeline for that? I'm working with JWST archive produces that have (very) bad WCS solutions, and I need to be able to access and work with the SIP versions in order to derive appropriate corrections. My workflow without CARTA is clunky: either I have to use in-notebook visualizations or ds9. |
Files with FITS SIP headers won't spatially match. I'm not certain it's the SIP's fault, but maybe.
This is a JWST
_cal.fits
file - you can get these from MAST in the L2 (level 2) pipeline products for any NIRCam observations.Header:
The coordinates are displayed, though:
The text was updated successfully, but these errors were encountered: