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
BugFix for PseudoTop construction in dilepton channel using proper lepton charges #16190
BugFix for PseudoTop construction in dilepton channel using proper lepton charges #16190
Conversation
…ith accordingly related charge from second lepton.
…ed to PseudoTop using recalculated lepton charges. In some cases, old implementation was leading to construction of objects using proper four-vectors, but with charges/PdgIDs corresponding to respective anti-particles.
A new Pull Request was created by @msavitskyi for CMSSW_8_1_X. It involves the following packages: TopQuarkAnalysis/TopEventProducers @cmsbuild, @monttj, @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 is ready @slava77 comparisons for the following workflows were not done due to missing matrix map:
|
+1 |
This pull request is fully signed and it will be integrated in one of the next CMSSW_8_1_X IBs (tests are also fine). This pull request requires discussion in the ORP meeting before it's merged. @slava77, @davidlange6, @smuzaffar |
+1 |
The bugfix needed to avoid cases, when Top Quark/ W-Plus / Anti-Lepton / B-jet are filled with charge/PdgIds corresponding to respective anti-particles (and vice versa), while keeping the original four-vectors (as associated to particular lepton). After the occurrence of such cases, an object collection (let's say, Anti-Leptons) actually is a mix of true Anti-Leptons and fakes from true Leptons (opposite for original Leptons collection). More detailed explanation of code's performance without bugfix is given in HN message "1" as indicated below, while message "2" leads to performance plots before/after bugfix.
Please check these messages on the HyperNews: