Fix scalar point-estimate shape for generic trackers - #5344
Merged
Conversation
Contributor
✅MegaLinter analysis: Success
Notices
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
|
FlorianPfaff
marked this pull request as ready for review
August 18, 2026 19:16
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.

What changed
AbstractFilter.get_point_estimate()withatleast_1dso a one-dimensional state is represented as a length-1 state vector instead of a scalar.VonMisesFilterinsideTrackManagerand verifies the extracted point-estimate matrix has shape(1, 1).Why
TrackManager.get_point_estimate()stacks per-track estimates along axis 1. Circular distributions can return scalar means, so a valid one-dimensional filter caused stacking to fail with an axis error. Other generic tracker code already assumesget_point_estimate().shape[0]exists, so normalizing at the base-filter interface makes the API consistent.Validation
Created as a draft so repository CI can validate the backend matrix before merge.