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

PUPPI MET in RECO #29769

Conversation

ahinzmann
Copy link
Contributor

Clone of #29254 and #29768, with a fix for MET JER uncertainties to adress issue #29744.

PR description:

This PR computes puppiNoLep weights and puppi MET in RECO and stores the puppiNoLep weight as a value map. PUPPI MET is clustered based on standard PF candidates together with the value map of weights. A new boolean "isWeighted" is added to the reco::PFMet interface to indicate whether weights were applied during jet clustering. The packed candidates pick up the value map such that puppi does not need to be re-computed in MiniAOD.

The same was done for the puppi and PUPPI jets in #28936.

Other changes:

  • Produce puppiForMET directly in PuppiProducer instead of a two step procedure puppiNoLep->puppiForMET and rename it to puppiNoLep, consistent with the name in PackedCandidates
  • Implement fillDescriptions for PFMetProducer
  • Rename PFMET_cfi to pfMet_cfi everywhere (for consistency with the module name)
  • Fix input jet collection of pfMetEI
  • Remove pfMetEI from RecoMET_EventContent (however, leave EITopPAG_EventContent_cff untouched)
  • Resolve issue cleanup miniAOD workflow after moving PUPPI to reco #29264
  • By moving to the same input PF candidate collection for puppi MET and puppi jets (with just different weights), PUPPI MET significance and unclustered pT computation then don't rely on dR matching as implemented in Fix MET unclustered energy computation #29331 anymore.
  • Store ref to PF candidate inside pat muons (just like done for all other PAT objects). PUPPI MET significance and unclustered pT computation then don't rely on dR matching as implemented in Fix MET Significance, Covariance Matrix and unclustered energy lepton subtraction #29385 anymore.
  • Fix particle multiplicity computation in xy-correction for PUPPI MET. Previously, particles with a weight of 0 could also count in the multiplicity as a function of which the xy-corrections are computed. Since xy-correction are not needed/recommended for PUPPI MET, this fix is not backported.
  • For HI workflows, raise candidate pT threshold for chsMet and trkMet to 999. consistent with pfMet.

PR validation:

runTheMatrix -l limited

if this PR is a backport please specify the original PR and why you need to backport that PR:

No backport foreseen.

@cmsbuild
Copy link
Contributor

cmsbuild commented May 7, 2020

The code-checks are being triggered in jenkins.

@cmsbuild
Copy link
Contributor

cmsbuild commented May 8, 2020

+code-checks

Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-29769/15217

@cmsbuild
Copy link
Contributor

cmsbuild commented May 8, 2020

A new Pull Request was created by @ahinzmann for master.

It involves the following packages:

CommonTools/ParticleFlow
CommonTools/PileupAlgos
DataFormats/METReco
DataFormats/PatCandidates
ElectroWeakAnalysis/Utilities
HLTriggerOffline/Exotica
JetMETCorrections/Type1MET
PhysicsTools/PatAlgos
PhysicsTools/PatUtils
RecoMET/Configuration
RecoMET/METAlgorithms
RecoMET/METProducers

@perrotta, @andrius-k, @kmaeshima, @schneiml, @cmsbuild, @jfernan2, @fioriNTU, @slava77, @santocch can you please review it and eventually sign? Thanks.
@rappoccio, @gouskos, @hatakeyamak, @emilbols, @peruzzim, @seemasharmafnal, @mmarionncern, @jdolen, @smoortga, @missirol, @ferencek, @rovere, @jdamgov, @nhanvtran, @gkasieczka, @schoef, @mtosi, @mariadalfonso, @clelange, @riga, @JyothsnaKomaragiri, @mverzett, @cbernet, @gpetruc, @andrzejnovak this is something you requested to watch as well.
@silviodonato, @dpiparo you are the release manager for this.

cms-bot commands are listed here

@slava77
Copy link
Contributor

slava77 commented May 8, 2020

@cmsbuild please test workflow 25202.0, 25213.0, 250206.182, 25403.18, 250203.18, 250402.18, 11025.0, 11634.7, 25403.18, 250402.18, 11834.0, 25211.18, 25403.0, 250205.18

@cmsbuild
Copy link
Contributor

cmsbuild commented May 8, 2020

The tests are being triggered in jenkins.
Test Parameters:

@cmsbuild
Copy link
Contributor

cmsbuild commented May 8, 2020

+1
Tested at: 01dd1d4
https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-dde9e7/6168/summary.html
CMSSW: CMSSW_11_1_X_2020-05-07-2300
SCRAM_ARCH: slc7_amd64_gcc820

@cmsbuild
Copy link
Contributor

cmsbuild commented May 8, 2020

Comparison job queued.

@cmsbuild
Copy link
Contributor

cmsbuild commented May 8, 2020

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

@slava77 comparisons for the following workflows were not done due to missing matrix map:

  • /data/cmsbld/jenkins/workspace/compare-root-files-short-matrix/data/PR-dde9e7/250203.18_H125GGgluonfusion_13UP18+H125GGgluonfusion_13UP18+DIGIPRMXUP18_PU25+RECOPRMXUP18_PU25+HARVESTUP18_PU25
  • /data/cmsbld/jenkins/workspace/compare-root-files-short-matrix/data/PR-dde9e7/250205.18_ZTT_13UP18+ZTT_13UP18+DIGIPRMXUP18_PU25+RECOPRMXUP18_PU25+HARVESTUP18_PU25
  • /data/cmsbld/jenkins/workspace/compare-root-files-short-matrix/data/PR-dde9e7/250206.182_ZMM_13UP18_RD+ZMM_13UP18_RD+DIGIPRMXUP18_PU25_RD+RECOPRMXUP18_PU25_L1TMuDQM_RD+HARVESTUP18_PU25_L1TMuDQM_RD
  • /data/cmsbld/jenkins/workspace/compare-root-files-short-matrix/data/PR-dde9e7/250402.18_TTbar_13+FS_TTbar_13_PRMXUP18_PU50+HARVESTUP18FS+MINIAODMCUP18FS
  • /data/cmsbld/jenkins/workspace/compare-root-files-short-matrix/data/PR-dde9e7/25211.18_GluGluHToZZTo4L_M125_Pow_py8_Evt_13UP18+GluGluHToZZTo4L_M125_Pow_py8_Evt_13UP18+DIGIUP18_PU25+RECOUP18_PU25+HARVESTUP18_PU25
  • /data/cmsbld/jenkins/workspace/compare-root-files-short-matrix/data/PR-dde9e7/25403.0_H125GGgluonfusion_13+FS_H125GGgluonfusion_13_UP15_PU25+HARVESTUP15FS+MINIAODMCUP15FS
  • /data/cmsbld/jenkins/workspace/compare-root-files-short-matrix/data/PR-dde9e7/25403.18_H125GGgluonfusion_13+FS_H125GGgluonfusion_13_UP18_PU50+HARVESTUP18FS+MINIAODMCUP18FS

Comparison Summary:

  • No significant changes to the logs found
  • ROOTFileChecks: Some differences in event products or their sizes found
  • Reco comparison results: 142 differences found in the comparisons
  • DQMHistoTests: Total files compared: 34
  • DQMHistoTests: Total histograms compared: 2697527
  • DQMHistoTests: Total failures: 105
  • DQMHistoTests: Total nulls: 0
  • DQMHistoTests: Total successes: 2697103
  • DQMHistoTests: Total skipped: 319
  • DQMHistoTests: Total Missing objects: 0
  • DQMHistoSizes: Histogram memory added: 0.0 KiB( 33 files compared)
  • Checked 147 log files, 16 edm output root files, 34 DQM output files

@jfernan2
Copy link
Contributor

jfernan2 commented May 8, 2020

@ahinzmann Is this PR also fixing this small differences created in the past:
#29254 (comment)
Thanks

@ahinzmann
Copy link
Contributor Author

@ahinzmann Is this PR also fixing this small differences created in the past:
#29254 (comment)
Thanks

No

@slava77
Copy link
Contributor

slava77 commented May 8, 2020

+1

for #29769 01dd1d4

  • this looks as an appropriate bugfix to the issue in PUPPI MET in RECO #29254
  • jenkins tests pass and comparisons with the baseline appear to be in the same places as for PUPPI MET in RECO #29254 itself
  • the extra matrix tests confirm that the crash is not happening anymore in ShiftedParticleMETcorrInputProducer.cc, as expected

@jfernan2
Copy link
Contributor

jfernan2 commented May 8, 2020

+1

@silviodonato
Copy link
Contributor

merge

@cmsbuild cmsbuild merged commit 60e3a2a into cms-sw:master May 9, 2020
@santocch
Copy link

+1

@cmsbuild
Copy link
Contributor

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 be automatically merged.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

6 participants