-
Notifications
You must be signed in to change notification settings - Fork 177
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fix: Track state range is invalid if tip index is #1995
fix: Track state range is invalid if tip index is #1995
Conversation
This changes the track state ranges to return zero-length ranges in case the tip index is kInvalid. The VectorTrackContainer backend initializes the `tipIndex` to kInvalid, and so does the `addTrack`, so in principle this should always be consistent by default.
Maybe you could review this @EdwardMoyse? |
📊 Physics performance monitoring for 3b58c8dFull report VertexingSeedingCKFAmbiguity resolutionTruth tracking (Kalman Filter)Truth tracking (GSF) |
This looks good to me. |
Codecov Report
@@ Coverage Diff @@
## main #1995 +/- ##
=======================================
Coverage 49.80% 49.80%
=======================================
Files 413 413
Lines 23596 23606 +10
Branches 10676 10681 +5
=======================================
+ Hits 11753 11758 +5
- Misses 4342 4343 +1
- Partials 7501 7505 +4
📣 We’re building smart automated test selection to slash your CI/CD build times. Learn more |
This changes the track state ranges to return zero-length ranges in case the tip index is kInvalid. The VectorTrackContainer backend initializes the
tipIndex
to kInvalid, and so does theaddTrack
, so in principle this should always be consistent by default.Fixes #1994