[WIP] Track cluster matching #8
Open
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
For now the matching is just to the first track, will add some logic to this to select best match shortly
Update misleading comment
kdlong
force-pushed
the
trackClusterMatching
branch
from
94322db to
20b4767
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Sorry this is also caught up in the merge of Thomas' truth work
New producer for track and cluster links. Takes a PFCandidateCollection (presumably without track refs, though this is not enforced) and creates refs based on eta/phi matching with tracks.
It uses the TICLLayerTile class to put charged PFCands and tracks in separate eta/phi grids, then finds the best matches in a given grid. Right now the algorithm for "best match" is still being determined.