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

Use ECAL ratio timing algorithm for Run 1 and Run 2, and CC timing algorithm for Run 3 and beyond #42928

Merged
merged 2 commits into from
Oct 10, 2023

Conversation

thomreis
Copy link
Contributor

@thomreis thomreis commented Oct 2, 2023

PR description:

This PR sets the default ECAL timing algorithm to the ratio method. This is the default timing algorithm for Run 1 and Run 2.
For Run 3 and Phase 2 a new modifier run3_ecal is used to change the timing algorithm to CC timing and use different records with the label 'CC' for the timing calibrations and timing offset constants.

Note that this behaviour is different than what was discussed in the meeting on the 27th Sept. when the plan was made to make the CC timing the default and use eras to modify Run 1 and Run 2 configurations to use the ratio method. Since Run 1 configurations could not be modified using eras we decided to reverse the behaviour as in the description above.

PR validation:

The PR passes Run 1 and Run2 WFs in the limited matrix tests but currently fails all Run 3 and Phase 2 WFs because the consumed records with the 'CC' label are not yet in the GTs.

@thomreis
Copy link
Contributor Author

thomreis commented Oct 2, 2023

type ecal

@cmsbuild cmsbuild added the ecal label Oct 2, 2023
@cmsbuild
Copy link
Contributor

cmsbuild commented Oct 2, 2023

+code-checks

Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-42928/37070

  • This PR adds an extra 24KB to repository

@cmsbuild
Copy link
Contributor

cmsbuild commented Oct 2, 2023

A new Pull Request was created by @thomreis (Thomas Reis) for master.

It involves the following packages:

  • Configuration/Eras (operations)
  • RecoLocalCalo/EcalRecProducers (reconstruction)

@rappoccio, @fabiocos, @davidlange6, @jfernan2, @cmsbuild, @antoniovilela, @mandrenguyen can you please review it and eventually sign? Thanks.
@Martin-Grunewald, @thomreis, @apsallid, @fabiocos, @youyingli, @rchatter, @argiro, @makortel, @wang0jin, @missirol, @AnnikaStein this is something you requested to watch as well.
@antoniovilela, @sextonkennedy, @rappoccio you are the release manager for this.

cms-bot commands are listed here

@saumyaphor4252
Copy link
Contributor

@cmsbuild, please test

@cmsbuild
Copy link
Contributor

cmsbuild commented Oct 2, 2023

-1

Failed Tests: UnitTests RelVals RelVals-INPUT AddOn
Summary: https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-cefc69/35015/summary.html
COMMIT: 0e5e58d
CMSSW: CMSSW_13_3_X_2023-10-02-1100/el8_amd64_gcc11
User test area: For local testing, you can use /cvmfs/cms-ci.cern.ch/week1/cms-sw/cmssw/42928/35015/install.sh to create a dev area with all the needed externals and cmssw changes.

Unit Tests

I found 3 errors in the following unit tests:

---> test TestDQMOnlineClient-ecal_dqm_sourceclient had ERRORS
---> test TestDQMOnlineClient-visualization had ERRORS
---> test TestDQMOnlineClient-visualization_secondInstance had ERRORS

RelVals

----- Begin Fatal Exception 02-Oct-2023 21:29:41 CEST-----------------------
An exception of category 'NoProductResolverException' occurred while
   [0] Processing  Event run: 346512 lumi: 250 event: 243042266 stream: 0
   [1] Running path 'dqmoffline_step'
   [2] Prefetching for module DQMMessageLogger/'DQMMessageLogger'
   [3] Prefetching for module LogErrorHarvester/'logErrorHarvester'
   [4] Prefetching for module EcalRecHitProducer/'ecalRecHit@cpu'
   [5] Calling method for module EcalUncalibRecHitProducer/'ecalMultiFitUncalibRecHit@cpu'
Exception Message:
No data of type "EcalTimeOffsetConstant" with label "CC" in record "EcalTimeOffsetConstantRcd"
 Please add an ESSource or ESProducer to your job which can deliver this data.
----- End Fatal Exception -------------------------------------------------
----- Begin Fatal Exception 02-Oct-2023 21:29:56 CEST-----------------------
An exception of category 'NoProductResolverException' occurred while
   [0] Processing  Event run: 346512 lumi: 250 event: 243042266 stream: 0
   [1] Running path 'dqmoffline_13_step'
   [2] Prefetching for module SMPDQM/'SMPDQM'
   [3] Prefetching for module MuonProducer/'muons'
   [4] Prefetching for module MuonIdProducer/'muons1stStep'
   [5] Prefetching for module EcalRecHitProducer/'ecalRecHit@cpu'
   [6] Calling method for module EcalUncalibRecHitProducer/'ecalMultiFitUncalibRecHit@cpu'
Exception Message:
No data of type "EcalTimeOffsetConstant" with label "CC" in record "EcalTimeOffsetConstantRcd"
 Please add an ESSource or ESProducer to your job which can deliver this data.
----- End Fatal Exception -------------------------------------------------
----- Begin Fatal Exception 02-Oct-2023 21:34:10 CEST-----------------------
An exception of category 'NoProductResolverException' occurred while
   [0] Processing  Event run: 346512 lumi: 250 event: 243042266 stream: 0
   [1] Running path 'dqmofflineOnPAT_1_step'
   [2] Prefetching for module SingleTopTChannelLeptonDQM_miniAOD/'singleTopElectronMediumDQM_miniAOD'
   [3] Prefetching for module PATMuonSlimmer/'slimmedMuons'
   [4] Prefetching for module PATMuonSelector/'selectedPatMuons'
   [5] Prefetching for module PATMuonProducer/'patMuons'
   [6] Prefetching for module MuonProducer/'muons'
   [7] Prefetching for module MuonIdProducer/'muons1stStep'
   [8] Prefetching for module EcalRecHitProducer/'ecalRecHit@cpu'
   [9] Calling method for module EcalUncalibRecHitProducer/'ecalMultiFitUncalibRecHit@cpu'
Exception Message:
No data of type "EcalTimeOffsetConstant" with label "CC" in record "EcalTimeOffsetConstantRcd"
 Please add an ESSource or ESProducer to your job which can deliver this data.
----- End Fatal Exception -------------------------------------------------
Expand to see more relval errors ...

RelVals-INPUT

  • 139.005139.005_AlCaPhiSym2021/step2_AlCaPhiSym2021.log
  • 138.4138.4_PromptCollisions2021/step2_PromptCollisions2021.log
  • 138.5138.5_ExpressCollisions2021/step2_ExpressCollisions2021.log
Expand to see more relval errors ...

AddOn Tests

----- Begin Fatal Exception 02-Oct-2023 21:34:50 CEST-----------------------
An exception of category 'NoProductResolverException' occurred while
   [0] Processing  Event run: 1 lumi: 1 event: 4 stream: 3
   [1] Running path 'FEVTDEBUGHLToutput_step'
   [2] Prefetching for module PoolOutputModule/'FEVTDEBUGHLToutput'
   [3] Prefetching for module CaloTowersCreator/'towerMaker'
   [4] Prefetching for module EcalRecHitProducer/'ecalRecHit@cpu'
   [5] Calling method for module EcalUncalibRecHitProducer/'ecalMultiFitUncalibRecHit@cpu'
Exception Message:
No data of type "EcalTimeOffsetConstant" with label "CC" in record "EcalTimeOffsetConstantRcd"
 Please add an ESSource or ESProducer to your job which can deliver this data.
----- End Fatal Exception -------------------------------------------------
----- Begin Fatal Exception 02-Oct-2023 21:33:28 CEST-----------------------
An exception of category 'NoProductResolverException' occurred while
   [0] Processing  Event run: 1 lumi: 1 event: 1 stream: 1
   [1] Running path 'FEVTDEBUGHLToutput_step'
   [2] Prefetching for module PoolOutputModule/'FEVTDEBUGHLToutput'
   [3] Prefetching for module CaloTowersCreator/'towerMaker'
   [4] Prefetching for module EcalRecHitProducer/'ecalRecHit@cpu'
   [5] Calling method for module EcalUncalibRecHitProducer/'ecalMultiFitUncalibRecHit@cpu'
Exception Message:
No data of type "EcalTimeOffsetConstant" with label "CC" in record "EcalTimeOffsetConstantRcd"
 Please add an ESSource or ESProducer to your job which can deliver this data.
----- End Fatal Exception -------------------------------------------------
----- Begin Fatal Exception 02-Oct-2023 21:32:57 CEST-----------------------
An exception of category 'NoProductResolverException' occurred while
   [0] Processing  Event run: 1 lumi: 1 event: 1 stream: 1
   [1] Running path 'FEVTDEBUGHLToutput_step'
   [2] Prefetching for module PoolOutputModule/'FEVTDEBUGHLToutput'
   [3] Prefetching for module CaloTowersCreator/'towerMaker'
   [4] Prefetching for module EcalRecHitProducer/'ecalRecHit@cpu'
   [5] Calling method for module EcalUncalibRecHitProducer/'ecalMultiFitUncalibRecHit@cpu'
Exception Message:
No data of type "EcalTimeOffsetConstant" with label "CC" in record "EcalTimeOffsetConstantRcd"
 Please add an ESSource or ESProducer to your job which can deliver this data.
----- End Fatal Exception -------------------------------------------------
Expand to see more addon errors ...

@thomreis
Copy link
Contributor Author

thomreis commented Oct 3, 2023

As mentioned in the description exceptions of the NoProductResolverException are expected for this PR at the moment because the records are not yet in the GTs. @saumyaphor4252 if you are happy with the current result can we proceed and add them?

@saumyaphor4252
Copy link
Contributor

test parameters:

@saumyaphor4252
Copy link
Contributor

@cmsbuild, please test

Copy link
Contributor

@mmusich mmusich left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

just a minor suggestion, you can actually drop cms type specifications for extra safety.

@cmsbuild
Copy link
Contributor

cmsbuild commented Oct 6, 2023

-1

Failed Tests: Build
Summary: https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-cefc69/35079/summary.html
COMMIT: 3814335
CMSSW: CMSSW_13_3_X_2023-10-06-1100/el8_amd64_gcc11
User test area: For local testing, you can use /cvmfs/cms-ci.cern.ch/week1/cms-sw/cmssw/42928/35079/install.sh to create a dev area with all the needed externals and cmssw changes.

Build

I found compilation error when building:

>> Done generating edm plugin poisoned information
gmake[1]: *** [config/SCRAM/GMake/Makefile.rules:1937: CompilePython] Error 1
>> Plugins of all types refreshed.
gmake[1]: Target 'PostBuild' not remade because of errors.
gmake[1]: Leaving directory '/data/cmsbld/jenkins/workspace/ib-run-pr-tests/CMSSW_13_3_X_2023-10-06-1100'
gmake: *** [config/SCRAM/GMake/Makefile.rules:1825: src] Error 2
gmake: Target 'all' not remade because of errors.
gmake: *** [There are compilation/build errors. Please see the detail log above.] Error 2
+ eval scram build outputlog '&&' '(python3' /data/cmsbld/jenkins/workspace/ib-run-pr-tests/cms-bot/buildLogAnalyzer.py --logDir /data/cmsbld/jenkins/workspace/ib-run-pr-tests/CMSSW_13_3_X_2023-10-06-1100/tmp/el8_amd64_gcc11/cache/log/src '||' 'true)'
++ scram build outputlog
>> Entering Package Configuration/Eras


@saumyaphor4252
Copy link
Contributor

please test

  • Should work now, fixed a missing comma

@cmsbuild
Copy link
Contributor

cmsbuild commented Oct 6, 2023

+1

Summary: https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-cefc69/35084/summary.html
COMMIT: 3814335
CMSSW: CMSSW_13_3_X_2023-10-06-1100/el8_amd64_gcc11
User test area: For local testing, you can use /cvmfs/cms-ci.cern.ch/week1/cms-sw/cmssw/42928/35084/install.sh to create a dev area with all the needed externals and cmssw changes.

Comparison Summary

Summary:

  • You potentially added 130 lines to the logs
  • Reco comparison results: 19199 differences found in the comparisons
  • DQMHistoTests: Total files compared: 50
  • DQMHistoTests: Total histograms compared: 3356920
  • DQMHistoTests: Total failures: 8908
  • DQMHistoTests: Total nulls: 6
  • DQMHistoTests: Total successes: 3347984
  • DQMHistoTests: Total skipped: 22
  • DQMHistoTests: Total Missing objects: 0
  • DQMHistoSizes: Histogram memory added: -0.023 KiB( 49 files compared)
  • DQMHistoSizes: changed ( 4.53 ): -0.023 KiB JetMET/SUSYDQM
  • Checked 214 log files, 167 edm output root files, 50 DQM output files
  • TriggerResults: found differences in 5 / 48 workflows

@thomreis
Copy link
Contributor Author

thomreis commented Oct 6, 2023

We expect changes in the ECAL timing with this PR since before many workflows were using the default CC timing algorithm but with the ratio timing calibrations in the GTs. This should be fixed now with this PR.

@perrotta
Copy link
Contributor

urgent

  • ping @cms-sw/reconstruction-l2 @cms-sw/orp-l2 (for @cms-sw/operations-l2 )

@mandrenguyen
Copy link
Contributor

@thomreis
Copy link
Contributor Author

Yes it is possible that the changed timing has small effects on other distributions as well. Depending, e.g. how the out of time flag is set.

@mandrenguyen
Copy link
Contributor

+reconstruction
I see a change to quantities related to ECAL time, as intended, and then small changes to other ECAL related quantities which are also expected, as indicated here.

@rappoccio
Copy link
Contributor

+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.

7 participants