-
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
Add possibility to apply latest MET Phi corrections during MiniAOD processing #38461
Add possibility to apply latest MET Phi corrections during MiniAOD processing #38461
Conversation
+code-checks Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-38461/30671
|
A new Pull Request was created by @michaelwassmer for master. It involves the following packages:
@jpata, @cmsbuild, @clacaputo can you please review it and eventually sign? Thanks. cms-bot commands are listed here |
@cmsbuild please test |
+1 Summary: https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-ebeba3/25695/summary.html Comparison SummarySummary:
|
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 is actually one thing, where the input of experts would be greatly appreciated. It would probably be preferred to automatically retrieve the campaign and era, but at the moment I'm not sure how this could be achieved.
Don't we usually configure this on the fly with the era-dependent toModify
operations?
run2_muon_2016.toModify( process.patMuons, effectiveAreaVec = [0.0735,0.0619,0.0465,0.0433,0.0577]) |
} | ||
|
||
getattr(process, "patPFMetTxyCorr"+postfix).parameters = xyTags[corScheme+"_25ns"] | ||
print("DEBUG ",campaign,datamc,era) |
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.
unintentionally left in?
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.
Yes, I forgot that line. I just removed it and updated the PR.
Regarding the modifiers, are they also capable of differentiating between 'suberas' e.g. 2018B and 2018C? The corrections also differ between the these suberas.
Having a centrally available correction (option 2) would be preferred to a custom MiniAOD recipe. |
@michaelwassmer let me understand the final goal here, is this supposed to be backported to 10_6_X so it's used for UL ? |
This could be one use case to have phi corrected MET in the next MiniAOD interation out of the box. However, I asked the JME/MET conveners to join on Friday so we have their perspective as well. |
@cmsbuild please test |
+1 Summary: https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-ebeba3/25964/summary.html Comparison SummarySummary:
|
+reconstruction
|
@jpata I think your own |
Can |
unhold |
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. @perrotta, @dpiparo, @qliphy, @rappoccio (and backports should be raised in the release meeting by the corresponding L2) |
I was able to unhold, as I understanf this was a reco request |
please test |
+1 Summary: https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-ebeba3/26281/summary.html Comparison SummarySummary:
|
+1
|
PR description:
This PR is intended to allow the application of the latest MET Phi corrections when running over MiniAOD. The MET Phi corrections are intended to mitigate the observed azimuthal angle modulation of missing transverse momentum (MET). The corrections were derived by @lathomas and can be found at the following link: https://lathomas.web.cern.ch/lathomas/METStuff/XYCorrections/
This PR is just the CMSSW implementation of those corrections using an already existing module with some adaptions.
The effect of the PR can be seen in more detail in the following two presentations, which were given in the MET meeting:
Important: The PR is designed such that it shouldn't affect the default/current behavior at all.
For the PR to actually do something, the newly added 'campaign' and 'era' input arguments of the MET tool need to be explicitly used. This is actually one thing, where the input of experts would be greatly appreciated. It would probably be preferred to automatically retrieve the campaign and era, but at the moment I'm not sure how this could be achieved.
Changes:
PR validation:
Successfully performed
code-checks
andcode-format
.Besides some file read/open errors, the
runTheMatrix.py -l limited -i all
command also seemed to work successfully.