-
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
PuppiMET does not include latest JECs for Type-1 corrections in NanoAOD and missing uncertainties #30304
Comments
A new Issue was created by @saghosh Saranya Ghosh. @Dr15Jones, @silviodonato, @dpiparo, @smuzaffar, @makortel can you please review it and eventually sign/assign? Thanks. cms-bot commands are listed here |
Bringing to the notice of @ahinzmann , @lathomas , @peruzzim I have made the code changes required for a pull request [1]. Before opening a pull request, I wanted to ask about the line 219 [1] saghosh@ae4793e [2] https://github.com/cms-sw/cmssw/blob/master/PhysicsTools/NanoAOD/python/nano_cff.py#L219 [3] 88d684c |
assign reconstruction, xpog |
@saghosh In the latest Run2 release (10_6_X) Puppi is actually not using photon ID anymore and not calling switchOnVIDPhotonIdProducer anymore: |
Hello, thank you. |
Resolved with PR #30922 |
Reapplication of JECs for Type-1 corrections for PuppiMET is not performed to include the latest JECs during NanoAOD production.
https://github.com/cms-sw/cmssw/blob/master/PhysicsTools/NanoAOD/python/nano_cff.py#L198
This is particularly relevant for 2018D in which the MiniAOD is PROMPT RECO.
It is not possible to re-apply JECs on the fly since the AK4PuppiJet collection is not stored in NanoAOD.
Also uncertainties for PuppiMET, particularly UnclusteredEnergy Uncertainties and the JER, JES down uncertainties are missing.
Only part of the uncertainties were added previously : https://github.com/cms-nanoAOD/cmssw/pull/516/files
This issue is already raised in the NanoAOD git area :
cms-nanoAOD#523
The text was updated successfully, but these errors were encountered: