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

Coordinate transformation issue #1

Open
jdhenshaw opened this issue Mar 31, 2017 · 1 comment
Open

Coordinate transformation issue #1

jdhenshaw opened this issue Mar 31, 2017 · 1 comment

Comments

@jdhenshaw
Copy link
Owner

jdhenshaw commented Mar 31, 2017

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.

@jdhenshaw
Copy link
Owner Author

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.

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

1 participant