Allow larger motion in cam frames for solve #143
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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.