Deep merging of multiple tracks sets without using original matches #1865
+269
−28
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
servantftransperfect
force-pushed
the
dev/deepTrackMerge
branch
from
1a271a5 to
32d360c
Compare
servantftransperfect
force-pushed
the
dev/deepTrackMerge
branch
from
32d360c to
dcefe1a
Compare
mh0g
approved these changes
May 16, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Replace a simple and shallow track merger with a deep track merger :
Each track contains a list of observations. An observation is a featureId for a given view.
If two tracks observe the same [featureId/ viewId] (both using the same detector) then we consider that the two tracks should be merged together.