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
Reject 0 pt Puppi candidates in jet-track association #17626
Reject 0 pt Puppi candidates in jet-track association #17626
Conversation
A new Pull Request was created by @ferencek (Dinko Ferencek) for CMSSW_9_0_X. It involves the following packages: RecoBTag/ImpactParameter @cmsbuild, @cvuosalo, @slava77, @davidlange6 can you please review it and eventually sign? Thanks. cms-bot commands are listed here #13028 |
@cmsbuild please test |
The tests are being triggered in jenkins. |
Comparison job queued. |
given backport to 80X, I think it's worth keeping this in 90X as well |
This pull request is fully signed and it will be integrated in one of the next CMSSW_9_0_X IBs (tests are also fine). This pull request requires discussion in the ORP meeting before it's merged. @davidlange6, @smuzaffar |
+1 |
Charged PF candidates identified by the Puppi algorithm as pileup have their momenta scaled to 0. Consequently, eta and phi of such candidates are reset to 0 which can lead to spurious association of these candidates to jets whose axes point in the vicinity of (eta,phi)=(0,0). To reject such spurious associations, the candidate momentum is required to be greater than 0.
This change is completely transparent to all existing b-tagging algorithms and all monitored quantities. It manifests itself only in non-default setups where Puppi candidates are set as input for b tagging.