Adding pass-through option to MultiTrackSelector (for LST tracking / seeding) - LST-internal only#247
Adding pass-through option to MultiTrackSelector (for LST tracking / seeding) - LST-internal only#247
Conversation
|
run-ci: all |
|
The PR was built and ran successfully in standalone mode running on CPU. Here are some of the comparison plots.
The full set of validation and comparison plots can be found here. Here is a timing comparison: |
|
There was a problem while building and running with CMSSW. The logs can be found here. |
4ae573e to
2f5c077
Compare
|
run-ci: all |
|
The PR was built and ran successfully in standalone mode running on CPU. Here are some of the comparison plots.
The full set of validation and comparison plots can be found here. Here is a timing comparison: |
|
The PR was built and ran successfully with CMSSW running on CPU. Here are some plots. OOTB All Tracks
The full set of validation and comparison plots can be found here. |
| (trackingPhase2PU140 & (trackingLST | seedingLST)).toModify(highPtTripletStepSelector, passThroughForAll = True) | ||
| # Passthrough selector to satisfy the TrackListMerger requirement for selector values | ||
| highPtTripletStepSelectorLSTT4T5 = RecoTracker.FinalTrackSelectors.multiTrackSelector_cfi.multiTrackSelector.clone( | ||
| src = 'highPtTripletStepLSTT4T5Tracks', | ||
| passThroughForDisplaced = True, |
There was a problem hiding this comment.
which of these is making a change in plots_building_highPtTripletStep ?
Now that the selector functionality allows to select T4/T5 from the same collection, can we already use a merged collection?













As per title.
FYI: @bucket420, @slava77, @bdanzi