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
Add Muon L1 to prefire weight producer #33758
Conversation
@lathomas fyi |
+code-checks Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-33758/22709
|
A new Pull Request was created by @JanFSchulte (Jan-Frederik Schulte) for master. It involves the following packages: PhysicsTools/NanoAOD @perrotta, @gouskos, @cmsbuild, @fgolf, @slava77, @jpata, @mariadalfonso can you please review it and eventually sign? Thanks. cms-bot commands are listed here |
test parameters: pull_request = cms-data/PhysicsTools-PatUtils#2 |
please test |
-1 Failed Tests: UnitTests RelVals RelVals-INPUT Unit TestsI found errors in the following unit tests: ---> test runtestPhysicsToolsNanoAOD had ERRORS ---> test testTauEmbeddingProducers had ERRORS ---> test TestConfigDP had ERRORS RelVals
Expand to see more relval errors ...RelVals-INPUT
|
|
||
//Photons | ||
edm::Handle<std::vector<pat::Photon> > thePhotons; | ||
iEvent.getByToken(photons_token_, thePhotons); |
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.
Can you simplify with iEvent.get(token)?
https://twiki.cern.ch/twiki/bin/view/CMSPublic/SWGuideEDMGetDataFromEvent#get
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.
Done.
if ((dataeraMuon_.find("2016") != std::string::npos) && (eta > 1.24 && eta < 1.6) && | ||
(phi > 2.44346 && phi < 2.79253)) { | ||
if (parametrizationHotSpot_ == nullptr && !skipwarnings_) | ||
std::cout << "Prefiring parametrization not found, setting prefiring rate to 0 " << eta << " " << phi |
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.
Can you change the cout to LogError/Warning?
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.
Done.
#Next line will be updated once we get UL2016 maps | ||
run2_jme_2016.toModify( prefiringweight, DataEra = cms.string("2016BtoH")) | ||
run2_jme_2016.toModify( prefiringweight, DataEra = cms.string("2016BtoH"), DataEraMuon = cms.string("2016")) |
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.
better to redefine DataEra
as DataEraEcal
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.
Done.
Hi, How is the time-dependence within 2016 handled? For most analyses I think the best would be to provide separate weights for preVFP and postVFP in UL since this is how the MC is split. (Even if the actual measurement is done differently and the final numbers are produced from appropriate lumi-weighted averages) |
Hi @bendavid, yes, the pT turnons are taken from the L1 efficiency measurements and combined with the plateau value obtained in the unprefireable events. We have 11 bins in abs(eta), plus the additional hot spot Laurent found. We provide a wide range of options for analyzers for the 2016 dataset. In addition to the full year, 2016preVFP, 2016postVFP, 2016 B-G and 2016 H are all available. |
+code-checks Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-33758/23195
|
please test |
+1 Summary: https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-e4ab93/15800/summary.html Comparison SummarySummary:
|
+1
|
Wit this PR, we add muon weights on top of the ECAL. ECAL weights are also updated. Shown here the effect on the ttH mc sample, 2017 This PR updates in master on UL nanov8: The 10_6 backport, where we store the old weights Before the update, the weights were closer to 1. The decrease seems due to the muon weights |
To me it looks like the additional muon weights do shift the overall weight further away from 1 by a consistent amount in line with my expectation. |
agreed these numbers seem all reasonable and consistent. |
+xpog size, branch name and DQM plots consisted with PR description and follow up review |
This pull request is fully signed and it will be integrated in one of the next master IBs (tests are also fine). 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 |
This PR adds the muon L1 prefiring to the L1PrefireWeightProducer (renamed from L1ECALPrefireWeightProducer).
The prefiring probability has been measured to be 1.5% on average in 2016 up to and including Run G, and about 0.5% afterwards. Corrections for this effect as a function of muon eta and pT are derived and are made available via the usual prefiring weight producer.
The measurement of the effect is is documented in https://indico.cern.ch/event/1027400/contributions/4314164/attachments/2225456/3769418/20210413_L1Prefiring_JSchulte.pdf and the proposal for a correction in https://indico.cern.ch/event/1034615/contributions/4344897/attachments/2237683/3793236/20210503_L1Prefiring_JSchulte.pdf. The proposal, together with a validation of the procedure, will be presented in the PPD General Meeting on 5/20/2021: https://indico.cern.ch/event/1034467/.
The prefire weight producer is changed to produce a common prefire weight including both the ECAL and muon system effects. Individual weights for muons, photons, and jets. While for the ECAL prefiring, an eta-pT map is provided as a histogram, for muons TF1s with an analytical parametrization of the pT dependence in multiple bins of muon eta.
A new ROOT file with these parametrizations is added to the corresponding cms-data repository in this PR: cms-data/PhysicsTools-PatUtils#2