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
There is an issue with the generation of coordinates from fits headers. Obviously an issue for high dec/latitude sources.
Short term work around: Updated file_read.pro - For now make sure to use keyword /OFFSET
Slightly longer term work around: Work in pixels only
Longer term fix: Rewrite in python, use wcsaxes :-)
Worth noting that this doesn't affect any of the fitting process. Just the coordinates output at the end. Users should check the output coordinates with those generated from the fits header. The SCOUSE output can be easily updated to correct for any problems.
The text was updated successfully, but these errors were encountered:
Added /PIXELS keyword to file_read.pro - allows users to output coordinate pixels values - users will then have to create coordinates manually as a post-processing step.
Again - fitting process unaffected - only the output.
There is an issue with the generation of coordinates from fits headers. Obviously an issue for high dec/latitude sources.
Short term work around: Updated file_read.pro - For now make sure to use keyword /OFFSET
Slightly longer term work around: Work in pixels only
Longer term fix: Rewrite in python, use wcsaxes :-)
Worth noting that this doesn't affect any of the fitting process. Just the coordinates output at the end. Users should check the output coordinates with those generated from the fits header. The SCOUSE output can be easily updated to correct for any problems.
The text was updated successfully, but these errors were encountered: