Updating MET Significance Parameters with 80X Run2016 tune

[danbarto]

Updating the parameters for MET Significance with the latest tune (as used in JME-17-001).

[cmsbuild]

@danbarto, CMSSW_10_1_X branch is closed for direct updates. cms-bot is going to move this PR to master branch.
In future, please use cmssw master branch to submit your changes.

[cmsbuild]

The code-checks are being triggered in jenkins.

[cmsbuild]

+code-checks

Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-22315/3523

[cmsbuild]

A new Pull Request was created by @danbarto (Daniel) for master.

It involves the following packages:

RecoMET/METProducers

@perrotta, @cmsbuild, @slava77 can you please review it and eventually sign? Thanks.
@TaiSakuma, @gouskos, @ahinzmann, @mmarionncern, @jdamgov, @jdolen, @nhanvtran, @gkasieczka, @schoef, @mariadalfonso, @seemasharmafnal this is something you requested to watch as well.
@davidlange6, @slava77, @fabiocos you are the release manager for this.

cms-bot commands are listed here

[perrotta]

please test

[cmsbuild]

The tests are being triggered in jenkins.
https://cmssdt.cern.ch/jenkins/job/ib-any-integration/26257/console Started: 2018/02/23 11:29

[cmsbuild]

+1
Tested at: f7aacfd
https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-22315/26257/summary.html

[cmsbuild]

Comparison job queued.

[cmsbuild]

Comparison is ready
https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-22315/26257/summary.html

Comparison Summary:

• No significant changes to the logs found
• Reco comparison results: 36 differences found in the comparisons
• DQMHistoTests: Total files compared: 28
• DQMHistoTests: Total histograms compared: 2498056
• DQMHistoTests: Total failures: 1
• DQMHistoTests: Total nulls: 0
• DQMHistoTests: Total successes: 2497879
• DQMHistoTests: Total skipped: 176
• DQMHistoTests: Total Missing objects: 0
• DQMHistoSizes: Histogram memory added: 1.03000000001 KiB( 23 files compared)
• Checked 115 log files, 9 edm output root files, 28 DQM output files

[perrotta]

@danbarto Can you provide a link to the studies/presentations that lead to these new parameters?

[danbarto]

@perrotta Results are presented in JME-17-001. You can find a presentation from the JetMET workshop here: https://indico.cern.ch/event/639724/contributions/2593794/attachments/1459666/2254181/METSig_JMEWorkshopHelsinki.pdf

[perrotta]

This PR updates the patMET significance in all workflows, see e.g. RunSinglePh2017B wf 136.788 from jenkins:

The (almost one year old) slides linked in #22315 (comment) do not show the improvement with respect to what was the previous tune, unless it was what in the slides is labelled as "pure MET". Therefore, let ask for a POG endorsement through the MET reco contacts: @gouskos @jdamgov

Moreover: this "Run2016 tune" is applied to all data, older and newer that 2016: is it correct?

[gouskos]

Hi @perrotta, the comparison in these slides is vs "pure MET". The MET significance parameters in this PR are the latest we have in the MET group using the 2016 data. These are consistent with the ones used for the results presented in the run 2 paper [preapproved]. We will prepare a recipe so users can update the parameters on the fly., but the ones currently in miniAOD are quite old.

[perrotta]

+1

• MET significance parameters updated in miniAOD following the latest prescriptions of the MET group

[cmsbuild]

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. @davidlange6, @slava77, @smuzaffar, @fabiocos (and backports should be raised in the release meeting by the corresponding L2)

[fabiocos]

+1