Add min_num_neighbors constraint for spatial matching #3463
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
ahojnnes
reviewed
Jul 7, 2025
ahojnnes
reviewed
Jul 8, 2025
ahojnnes
reviewed
Jul 8, 2025
ahojnnes
approved these changes
Jul 8, 2025
Contributor
|
Thank you! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
This PR adds a
min_num_neighborsoption tospatial_matcher, ensuring that each image is matched with at least the specified number of neighbors. This makes matching more adaptive to different image distributions and removes the need to manually tunemax_distancein some cases.min_num_neighborstoSpatialMatchingOptions. When set to a positive value, the matcher will always include at least that number of neighbors, even if some exceed max_distanceCMakeUserPresets.jsonand.clangdto.gitignore