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

Make source_catalog output compatible with tweakreg #8639

Closed
stscijgbot-jp opened this issue Jul 9, 2024 · 1 comment · Fixed by spacetelescope/stcal#333
Closed

Make source_catalog output compatible with tweakreg #8639

stscijgbot-jp opened this issue Jul 9, 2024 · 1 comment · Fixed by spacetelescope/stcal#333

Comments

@stscijgbot-jp
Copy link
Collaborator

Issue JP-3686 was created on JIRA by Sarah Kendrew:

A common use case for astrometric alignment, especially for fields that are sparse in stars so aligning to Gaia doesn't work well, is to use the output catalog of one filter image as absolute reference catalog to align the other filters. Especially when the field coverage between filters is very similar, this works well. However the output of the source_catalog step puts the sky coordinates of the sources in a field called "sky_centroid", which contains SkyCoord objects (i.e. 2 comma-separated values for RA and Dec); the tweakreg step requires dedicated columns 'RA' and 'DEC' when a custom catalog is passed for the abs_refcat parameter. This means that for this common approach to astrometric alignment, the user always has to read in the catalog file, and convert the sky_centroid column to 2 separate RA and DEC columns. This is trivial, but it's an annoying extra step. 

It would be really nice if these steps could be joined up better, either by replacing the sky_centroid field in the source catalog by 2 separate RA and DEC columns, or by making the tweakreg step have the ability to read in SkyCoord objects. 

Perhaps there is a good reason why this isn't possible, or advised - please explain if that is the case!

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

Successfully merging a pull request may close this issue.

1 participant