-
Notifications
You must be signed in to change notification settings - Fork 4.4k
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
Extension of electron matching in nanoAOD (backport) #33347
Extension of electron matching in nanoAOD (backport) #33347
Conversation
A new Pull Request was created by @sscruz for CMSSW_10_6_X. It involves the following packages: PhysicsTools/HepMCCandAlgos @cmsbuild, @santocch, @mariadalfonso, @gouskos, @fgolf can you please review it and eventually sign? Thanks. cms-bot commands are listed here
|
this backport is not a 1:1 as you have now CandMCMatchTableProducer.cc and CandMCMatchTableProducerNew.cc |
please test |
backport |
indeed, i thought the safest way would be to duplicate the module for the time being... Adding a bool ExtendMatching should be possible, but I'd have to change some of the consumes to "mayConsumes". If you confirm this is the way to go, I can do it |
+1 Summary: https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-2b75ee/14110/summary.html Comparison SummarySummary:
|
yes, please try with this options (cloning files such as CandMCMatchTableProducerNew will be unmaintainable). |
9e8b02b
to
d7d836f
Compare
@mariadalfonso sorry it took so long, I missed your last message. Just one procedural question: I applied the code checks and that changes parts of the code I didn't mean to change. Is this correct for a backport? |
electronMCTableNew = cms.EDProducer("CandMCMatchTableProducer", | ||
src = electronTable.src, | ||
mcMapDressedLep = cms.InputTag("electronsMCMatchForTableAlt"), | ||
mcMap = cms.InputTag("electronsMCMatchForTable"), | ||
mapTauAnc = cms.InputTag("matchingElecPhoton:hasTauAnc"), | ||
objName = electronTable.name, | ||
objType = cms.string("ElectronDressed"), | ||
branchName = cms.string("genPart"), | ||
docString = cms.string("MC matching to status==1 electrons or photons"), | ||
genparticles = cms.InputTag("finalGenParticles"), | ||
) | ||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
this "electronMCTableNew" is not used anymore in any sequence.
we should add modification into electronMCTable and have a simple way to take or not the new settings.
electronSequence = cms.Sequence(bitmapVIDForEle + bitmapVIDForEleHEEP + isoForEle + ptRatioRelForEle + seedGainEle + slimmedElectronsWithUserData + finalElectrons) | ||
electronTables = cms.Sequence (electronMVATTH + electronTable) | ||
electronMC = cms.Sequence(electronsMCMatchForTable + electronMCTable) | ||
electronMCnew = cms.Sequence(particleLevelForMatching + tautaggerForMatching + matchingElecPhoton + electronsMCMatchForTable + electronsMCMatchForTableAlt + electronMCTableNew) | ||
( run2_nanoAOD_106Xv1 & ~run2_nanoAOD_devel).toReplaceWith(electronMC, electronMCnew) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
we should have the new sequence by default and then for the v8 ( run2_nanoAOD_106Xv1 & ~run2_nanoAOD_devel) we should run the old sequence.
can you confirm that runs on both
runTheMatrix -l 1325.81 ( #test ttbar 106Xv1 )
and runTheMatrix -l 1325.7 ( # test ttbar 94XMiniAODv2)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
thanks for the clarification, i misunderstood the meaning of the modifiers. I've just pushed the proper setting, along with some fixes. I confirm the runTheMatrix workflows are running properly
+1 Summary: https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-2b75ee/15301/summary.html Comparison SummarySummary:
|
please test |
+1 Summary: https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-2b75ee/15346/summary.html Comparison SummarySummary:
|
backport of #32966 |
+xpog results as in #33347 (comment) |
+1 |
This pull request is fully signed and it will be integrated in one of the next CMSSW_10_6_X IBs (tests are also fine) and once validation in the development release cycle CMSSW_12_0_X is complete. This pull request will now be reviewed by the release team before it's merged. @silviodonato, @dpiparo, @qliphy (and backports should be raised in the release meeting by the corresponding L2) |
+1 |
PR description:
Backport of #32966
Electron matching to MC truth has some inefficiency due to FSR. This PR extends the matching to recover such cases, by adding the possibility that electrons can be matched to gendressed particles. This issue has been reported here:
https://indico.cern.ch/event/962278/contributions/4060711/attachments/2136665/3599026/electron_matching_nano_nov4.pdf
and further discussed here:
cms-nanoAOD#552
The electron matching is performed as follows: