-
Notifications
You must be signed in to change notification settings - Fork 28
Adding trk.id leaf #326
Copy link
Copy link
Open
Labels
art / OfflineThis requires some touching of art / OfflineThis requires some touching of art / OfflineenhancementNew feature or requestNew feature or request
Metadata
Metadata
Assignees
Labels
art / OfflineThis requires some touching of art / OfflineThis requires some touching of art / OfflineenhancementNew feature or requestNew feature or request
Type
Fields
Give feedbackNo fields configured for issues without a type.
In order to help analyzers understand which track fits correspond to the same set of hits, we should use SelectSameTrack so that we can add a leaf that analyzers can more easily choose the best fit hypothesis for a given set of hits. We should add
trk.idandtrk.rankleaves so we would end up with something like:The algorithm for trk.rank is to be determined but would give the ranking of each hypothsis for that track.
Added 1/21/2026: note that we want the determination of ID and rank to be performed within an art module as a data product that is then read by the EventNtupleMaker module