You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Often I have to crop images, but the Physical coordinate, which is understood by SAO ds9, is missing when I use ccdproc.
I have my personal codes, which include image trimming and adds the IRAF-like LTV/LTM, and mimics IRAF IMCOPY. I guess it'll be better if such header keywords are included in ccdproc by default.
The following code simply makes a FITS file, trims it, and adds LTM/LTV keys.
I just wanted to bump this comment. I think having the LTV/LTM keywords is extremely valuable to delineate between the physical/image coordinate systems.
Often I have to crop images, but the
Physical
coordinate, which is understood by SAO ds9, is missing when I useccdproc
.I have my personal codes, which include image trimming and adds the IRAF-like LTV/LTM, and mimics IRAF
IMCOPY
. I guess it'll be better if such header keywords are included in ccdproc by default.The following code simply makes a FITS file, trims it, and adds LTM/LTV keys.
As can be seen, the
Physical
WCS works correctly on SAO ds9 (the cursor was at the lower-left corner of the trimmed image):EDIT: XY order was wrong in the original version of this issue... I corrected it.
The text was updated successfully, but these errors were encountered: