-
Notifications
You must be signed in to change notification settings - Fork 4.3k
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
[13.1.X] add information on first hit from HitPattern to LostTracks #42693
[13.1.X] add information on first hit from HitPattern to LostTracks #42693
Conversation
A new Pull Request was created by @mmusich (Marco Musich) for CMSSW_13_1_X. It involves the following packages:
@cmsbuild, @simonepigazzini, @mandrenguyen, @clacaputo, @vlimant can you please review it and eventually sign? Thanks. cms-bot commands are listed here |
type tracking |
please test |
+1 Summary: https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-cc4df2/34566/summary.html Comparison SummarySummary:
|
+1 |
+1 |
This pull request is fully signed and it will be integrated in one of the next CMSSW_13_1_X IBs (tests are also fine) and once validation in the development release cycle CMSSW_13_3_X is complete. This pull request will now be reviewed by the release team before it's merged. @rappoccio, @antoniovilela, @sextonkennedy (and backports should be raised in the release meeting by the corresponding L2) |
+1 |
backport of #42681
PR description:
Title says it all, as per request here.
It will add information about the first hit in the hit pattern for
lostTracks
with pT > 0.95 GeVcmssw/PhysicsTools/PatAlgos/python/slimming/lostTracks_cfi.py
Line 21 in 8922daa
similarly for what is already done for
packedPfCandidates
cmssw/PhysicsTools/PatAlgos/plugins/PATPackedCandidateProducer.cc
Lines 293 to 294 in 8922daa
cmssw/PhysicsTools/PatAlgos/python/slimming/packedPFCandidates_cfi.py
Line 19 in 8922daa
PR validation:
cmssw
compiles.On-file size increase in miniAOD has not been measured, but should be negligible as per reasoning in reference.
If this PR is a backport please specify the original PR and why you need to backport that PR. If this PR will be backported please specify to which release cycle the backport is meant for:
Verbatim backport of #42681 to 13.1.X (meant as as intermediate backport to downstream releases)