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

Add new ECAL PF RecHit thresholds for 2021 Run 3 MC #35233

Merged

Conversation

malbouis
Copy link
Contributor

@malbouis malbouis commented Sep 10, 2021

PR description:

This PR is to add a new ECAL tag, EcalPFRecHitThresholds_34sigma_TL235, to the 2021 Run-3 MC GTs as per request from the ECAL group (https://hypernews.cern.ch/HyperNews/CMS/get/calibrations/4462.html), aiming the Run 3 MC Campaign (in 120X).

The differences wrt the previous GTs are listed below.

2021 realistic
https://cms-conddb.cern.ch/cmsDbBrowser/diff/Prod/gts/121X_mcRun3_2021_realistic_v1/121X_mcRun3_2021_realistic_v2

2021 cosmics
https://cms-conddb.cern.ch/cmsDbBrowser/diff/Prod/gts/121X_mcRun3_2021cosmics_realistic_deco_v1/121X_mcRun3_2021cosmics_realistic_deco_v2

2021 heavy ion
https://cms-conddb.cern.ch/cmsDbBrowser/diff/Prod/gts/121X_mcRun3_2021_realistic_HI_v1/121X_mcRun3_2021_realistic_HI_v2

PR validation:

runTheMatrix.py -l 159.0,11634.0,7.23 --ibeos -j4

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

This PR will be backported to 120X.

@cmsbuild cmsbuild added this to the CMSSW_12_1_X milestone Sep 10, 2021
@malbouis malbouis changed the title Alca 121 x new ecalpf hit thresholds4mc run3 Add new ECAL PF RecHit thresholds for 2021 Run 3 MC Sep 10, 2021
@malbouis
Copy link
Contributor Author

test parameters:

workflows = 159.0,11634.0,7.23

@malbouis
Copy link
Contributor Author

test parameters:

  • workflows = 159.0,11634.0,7.23

@cmsbuild
Copy link
Contributor

+code-checks

Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-35233/25193

  • This PR adds an extra 12KB to repository

@cmsbuild
Copy link
Contributor

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

It involves the following packages:

  • Configuration/AlCa (alca)

@yuanchao, @malbouis, @cmsbuild, @tvami, @francescobrivio can you please review it and eventually sign? Thanks.
@Martin-Grunewald, @mmusich, @fabiocos, @tocheng this is something you requested to watch as well.
@perrotta, @dpiparo, @qliphy you are the release manager for this.

cms-bot commands are listed here

@malbouis
Copy link
Contributor Author

please test

@tvami
Copy link
Contributor

tvami commented Sep 10, 2021

urgent

  • the backport of this is needed for the PF calibration

@cmsbuild
Copy link
Contributor

+1

Summary: https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-617f1e/18506/summary.html
COMMIT: 3a67ae8
CMSSW: CMSSW_12_1_X_2021-09-10-1100/slc7_amd64_gcc900
User test area: For local testing, you can use /cvmfs/cms-ci.cern.ch/week1/cms-sw/cmssw/35233/18506/install.sh to create a dev area with all the needed externals and cmssw changes.

Comparison Summary

@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-617f1e/7.23_Cosmics_UP21+Cosmics_UP21+DIGICOS_UP21+RECOCOS_UP21+ALCACOS_UP21+HARVESTCOS_UP21

Summary:

  • No significant changes to the logs found
  • Reco comparison results: 4532 differences found in the comparisons
  • DQMHistoTests: Total files compared: 39
  • DQMHistoTests: Total histograms compared: 3001001
  • DQMHistoTests: Total failures: 1155
  • DQMHistoTests: Total nulls: 0
  • DQMHistoTests: Total successes: 2999824
  • DQMHistoTests: Total skipped: 22
  • DQMHistoTests: Total Missing objects: 0
  • DQMHistoSizes: Histogram memory added: 0.0 KiB( 38 files compared)
  • Checked 165 log files, 37 edm output root files, 39 DQM output files
  • TriggerResults: found differences in 2 / 38 workflows

@tvami
Copy link
Contributor

tvami commented Sep 11, 2021

Let me also tag @cms-sw/ecal-dpg-l2 @fcouderc (please also add any other relevant people)

@hatakeyamak
Copy link
Contributor

I went over observed changes quickly. Not surprising, there are quite a few changes in ECAL related reco quantities, so it's hard to digest all of them, but by looking at PF validation plots, I see that changes are specifically coming from PF photons [1], which we expect. This [2] shows PF photon candidate p distribution, and we see a big suppresion at low pt, which again we expect. So, the observed changes are certainly going in the direction we expect.

[1] https://cmssdt.cern.ch/SDT/jenkins-artifacts/baseLineComparisons/CMSSW_12_1_X_2021-09-10-1100+617f1e/45373/312.0_Pyquen_ZeemumuJets_pt10_2760GeV_2021+Pyquen_ZeemumuJets_pt10_2760GeV_2021+DIGIHI2021MIX+RECOHI2021MIX+HARVESTHI2021PPRECO/ParticleFlow_PackedCandidates.html

[2] https://cmssdt.cern.ch/SDT/jenkins-artifacts/baseLineComparisons/CMSSW_12_1_X_2021-09-10-1100+617f1e/45373/validateJR/all_OldVSNew_TTbar14TeV2021wf11634p0/all_OldVSNew_TTbar14TeV2021wf11634p0c_log10recoPFCandidates_particleFlow__RECO_obj_p72.png

@hatakeyamak
Copy link
Contributor

hatakeyamak commented Sep 12, 2021

Maybe the b-tagging conveners could take this? @johnalison @soureek

We should certainly hear from b-tag experts, but just sharing what I gathered form a quick look. From what I see, many of failures comes from low entry plots where the original blue ones have just one or only handful entries, and in new/test red ones some of the entries disappear. Due to increased PF ECAL thresholds, such behaviors don't seem too surprising.

@tvami
Copy link
Contributor

tvami commented Sep 13, 2021

+alca

  • The changes in the Jenkins tests are expected and understood
  • b-tagging was contacted privately to explain the changes in those plots

@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 now be reviewed by the release team before it's merged. @perrotta, @dpiparo, @qliphy (and backports should be raised in the release meeting by the corresponding L2)

@perrotta
Copy link
Contributor

+1

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

5 participants