Handle rare cases where KF track extrapolation fails #861
Conversation
This file contains 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
cbravo135
approved these changes
May 26, 2021
|
what branch is this? |
pbutti
approved these changes
Jun 2, 2021
|
Why is this not being merged to Master? |
|
This appears to have been on some private repo. |
|
Alic's fork is not private. I was easily able to pull and test his code with the information provided on this page due to how clear it is about what the PR is proposing. |
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.
Fixed rare bug in TrackClusterMatcherMinDistance. Check to make sure that trackstate at Ecal exists before matching Track to clusters. If no trackstate at Ecal, match this Track to null Cluster.