Reset CLEAR continuity across empty frames - #5174
Closed
FlorianPfaff wants to merge 2 commits into
Closed
Conversation
Contributor
✅MegaLinter analysis: Success
Notices📣 MegaLinter 9.5.0 is out! Discover the new features and security recommendations in the release announcement. (Skip this info by defining See detailed reports in MegaLinter artifacts Your project could benefit from a custom flavor, which would allow you to run only the linters you need, and thus improve runtime performances. (Skip this info by defining
|
Owner
Author
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
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.

Bug
evaluate_clear(...)retainedprevious_timestep_idwhen a frame had no ground-truth detections or no tracker detections.The next non-empty frame therefore received the 1000-point continuity bonus from the last non-empty frame rather than from the immediately preceding timestep. After a detection gap, this could force a lower-similarity assignment, suppress legitimate ID switches, and reduce the accumulated MOTP similarity.
Fix
Clear the immediate-timestep association state before continuing from either empty-frame branch. The separate
previous_idstate is intentionally preserved, so ID switches are still scored against the last historical match after the object reappears.Regression coverage
The new focused regression covers both gap forms:
In both cases, the post-gap frame must optimize by similarity without stale continuity, while still recording the resulting historical ID switches.
Validation
main;GitHub Actions is the authoritative full repository validation.