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

Test if AstrometryDB applies WCS solutions correctly #1790

Open
stscijgbot-hstdp opened this issue Apr 23, 2024 · 1 comment
Open

Test if AstrometryDB applies WCS solutions correctly #1790

stscijgbot-hstdp opened this issue Apr 23, 2024 · 1 comment

Comments

@stscijgbot-hstdp
Copy link
Collaborator

Issue HLA-1249 was created on JIRA by Steve Goldman:

The first task to solving HLA-1234 is to test the assertion the best solution obtained from the AstrometryDB is applied as the primary WCS.  (Use a fresh ipppssoot dataset - process the RAW files yourself so there is no WCS in the FLC/FLT headers).  Ideally, the best solution in the dataset is a FIT_SVM solution so you can see if the runastrodriz tries to override with a FIT_REL solution.

@stscijgbot-hstdp
Copy link
Collaborator Author

Comment by Steve Goldman on JIRA:

I did a runastrodriz run on a raw dataset (j9r743020_asn) produced using HSTCAL (no WCS) which resulted in WCS: IDC_4bb1536oj-FIT_REL_GSC242. The attached log shows the results. 

The log will show that the FIT_REL_GAIADR3 and FIT_REL_2MASS fit did not have enough matches. The "best" primary WCS is also compromised as the cross-match magnitudes are not correlated. 

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