Skip to content
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

JES uncertainty fix #240

Merged
merged 2 commits into from
Jun 7, 2020
Merged

JES uncertainty fix #240

merged 2 commits into from
Jun 7, 2020

Conversation

danbarto
Copy link
Contributor

There is a discrepancy of the propagation of JES variations to type-1 MET between CMSSW and NanoAOD-tools. Discussed here:
https://indico.cern.ch/event/921037/contributions/3869620/attachments/2042217/3420993/nanoaod_jes_talk_v2.pdf
The fix was tested for 2017 (with METv2 recipe) and 2018. Consistent results up to the numerical precision of nanoAOD and the following bin migrations are now achieved.

@danbarto
Copy link
Contributor Author

Just to clarify: This fix only concerns JES. The closure of JER uncertainties/variations of miniAOD/nanoAOD is still under investigation.

@AndreasAlbert
Copy link
Contributor

Thanks @danbarto!

IIUC, the main issue fixed here is the selection of jets for which the uncertainty is propagated to MET, i.e. this line here. The way it is implemented right now, the exact same set of jets is used for
a) calculating T1 MET and JES uncertainties
b) calculating T1 smeared MET and JER uncertainties

Is that is the right approach in principle? If maybe someone from JME knows the answer for certain, that could guide the further investigation of the JER-related behavior.

@danbarto
Copy link
Contributor Author

To be honest, I'm not entirely sure what should be done if JER smeared jets are used in type-1 MET. The current implementation still resembles the "original" nanoAOD-tools implementation, just with proper type-1 corrections for JES.
Maybe @ahinzmann or @lathomas can comment?

@fgolf fgolf merged commit 5173142 into cms-nanoAOD:master Jun 7, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

3 participants