-
Notifications
You must be signed in to change notification settings - Fork 0
DM-20746: Defer to camera geometry instead of raw formatter for intiial WCS. #323
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
base: main
Are you sure you want to change the base?
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good.
Rereading the comments on the Jira ticket, I see that this is not supposed to be merged with the other PRs. |
9ac055f
to
b9bcd2b
Compare
Is this still relevant? (Also, typo in the commit message) |
This is a small cleanup (reducing reliance on a middleware interface we'd prefer to stop treating as public) that should only be merged after the 'camera' datasets in all LATISS repos have been rebuilt with post-DM-20746 code.
b9bcd2b
to
3a0d5e5
Compare
Yes, this is still relevant, but I haven't been paying attention to whether the precondition has been met (though if prompt processing no longer cares about LATISS, that's another way to satisfy it). I've rebased and fixed the commit message. |
We are still using LATISS data for integration testing, but I have no idea how to recognize a "rebuilt camera". Will it fail spectacularly if we try to run it on an incompatible repo? |
Yes, I expect you'll see astrometry-solving failures a large fraction of the time if the camera hasn't been rebuilt. If the camera has been rebuilt, you should see:
return |
Basic tests ( A run of 38 (independently selected) LATISS visits on |
That seems like a fairly high failure rate, but I don't have a good baseline for LATISS. Is this |
It looks like the camera in |
Re: the failure rate, the imaging pipeline has never been optimized for LATISS. That's why I did the We have our own dev repo, but I don't know when or from where the camera was last sourced. @hsinfang might know. |
This is a small cleanup (reducing reliance on a middleware interface we'd prefer to stop treating as public) that should only be merged after the 'camera' datasets in all LATISS repos have been rebuilt with post-DM-20746 code.