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

Allow larger motion in cam frames for solve #143

Merged
merged 1 commit into from
Feb 20, 2024
Merged

Conversation

brickbots
Copy link
Owner

When testing the new Cedar solver, I noticed that the PiFinder would take longer than expected to achieve first solve after moving the scope.

Turns out this has nothing to do with the new solver, but seems to be an overly aggressive image rejection. Due to slight bounce/vibration it's not uncommon for the scope/imu to take an extra exposure (or two!) to hit the very low motion-during-exposure threshold for resuming plate solving.

I'm betting that some of these exposures are worth trying to solve. Especially with the new Cedar system. Worse comes to worse, the solve fails and the system is no worse off than it was as the solver failure is usually very graceful.

This change really needs to be tested under the stars more, along with overall Cedar changes.

@brickbots brickbots merged commit b66e882 into main Feb 20, 2024
2 checks passed
@brickbots brickbots deleted the adj_img_reject branch February 20, 2024 01:08
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

Successfully merging this pull request may close these issues.

1 participant