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 PPS DAQ mapping to 13_3_X real data Run2 and Run3 GTs #43226

Merged
merged 2 commits into from
Nov 17, 2023

Conversation

perrotta
Copy link
Contributor

@perrotta perrotta commented Nov 8, 2023

PR description:

It adds the PPS DAQ mapping to 13_3_X real data GTs.
At the moment, no MC GTs are updated for it, because MC workflows do not consume the added payload yet.

They were announced in this CMSTalk post

=== Data Tags (all added with "hlt" synchronization):

PPSDAQMapping_TimingDiamond_v1
PPSDAQMapping_TrackingStrip_v1
PPSDAQMapping_TotemTiming_v1
PPSDAQMapping_TotemT2_v1
PPSAnalysisMask_v1

=== GT diffs

run2_data: https : //cms-conddb.cern.ch/cmsDbBrowser/diff/Prod/gts/133X_dataRun2_v1/133X_dataRun2_v2
run2_data_HEfail : https://cms-conddb.cern.ch/cmsDbBrowser/diff/Prod/gts/133X_dataRun2_HEfail_v1/133X_dataRun2_Hefail_v2
run2_data_promptlike_hi : https://cms-conddb.cern.ch/cmsDbBrowser/diff/Prod/gts/133X_dataRun2_PromptLike_HI_v1/133X_dataRun2_PromptLike_HI_v2
run2_hlt_relval : https://cms-conddb.cern.ch/cmsDbBrowser/diff/Prod/gts/133X_dataRun2_HLT_relval_v1/133X_dataRun2_HLT_relval_v2
run3_hlt : https://cms-conddb.cern.ch/cmsDbBrowser/diff/Prod/gts/133X_dataRun3_HLT_frozen_v1/133X_dataRun3_HLT_frozen_v2
run3_data_express : https://cms-conddb.cern.ch/cmsDbBrowser/diff/Prod/gts/133X_dataRun3_Express_frozen_v1/133X_dataRun3_Express_frozen_v2
run3_data_prompt : https://cms-conddb.cern.ch/cmsDbBrowser/diff/Prod/gts/133X_dataRun3_Prompt_frozen_v1/133X_dataRun3_Prompt_frozen_v2
run3_data : https://cms-conddb.cern.ch/cmsDbBrowser/diff/Prod/gts/133X_dataRun3_v3/133X_dataRun3_v4
run3_data_PromptAnalysis : https://cms-conddb.cern.ch/cmsDbBrowser/diff/Prod/gts/133X_dataRun3_PromptAnalysis_v2/133X_dataRun3_PromptAnalysis_v3

@perrotta
Copy link
Contributor Author

perrotta commented Nov 8, 2023

please test with #43226

@perrotta perrotta changed the title Add PPS DAQ mapping to 13_3_X real data GTs [DO NOT MERGE] Add PPS DAQ mapping to 13_3_X real data GTs Nov 8, 2023
@perrotta perrotta marked this pull request as ready for review November 8, 2023 17:13
@cmsbuild
Copy link
Contributor

cmsbuild commented Nov 8, 2023

+code-checks

Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-43226/37573

@cmsbuild
Copy link
Contributor

cmsbuild commented Nov 8, 2023

A new Pull Request was created by @perrotta (Andrea Perrotta) for master.

It involves the following packages:

  • Configuration/AlCa (alca)

@perrotta, @saumyaphor4252, @consuegs can you please review it and eventually sign? Thanks.
@yuanchao, @Martin-Grunewald, @missirol, @rsreds, @tocheng, @mmusich, @fabiocos this is something you requested to watch as well.
@rappoccio, @sextonkennedy, @antoniovilela you are the release manager for this.

cms-bot commands are listed here

@cmsbuild
Copy link
Contributor

cmsbuild commented Nov 8, 2023

+code-checks

Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-43226/37575

@cmsbuild
Copy link
Contributor

cmsbuild commented Nov 8, 2023

Pull request #43226 was updated. @consuegs, @cmsbuild, @perrotta, @saumyaphor4252 can you please check and sign again.

@perrotta perrotta changed the title [DO NOT MERGE] Add PPS DAQ mapping to 13_3_X real data GTs Add PPS DAQ mapping to 13_3_X real data Run2 and Run3 GTs Nov 9, 2023
@perrotta
Copy link
Contributor Author

perrotta commented Nov 9, 2023

Waiting for #43197 to get merged first. Then a rebase will be probably needed

@francescobrivio
Copy link
Contributor

Then a rebase will be probably needed

Maybe not, given I'm updating MC GTs only, while you are touching data GTs. GH should be (hopefully) smart enough!

@perrotta
Copy link
Contributor Author

Then a rebase will be probably needed

Maybe not, given I'm updating MC GTs only, while you are touching data GTs. GH should be (hopefully) smart enough!

Indeed, github was smart enough to recognize that changes were applied on different lines, even if nearby

@perrotta
Copy link
Contributor Author

please test
(just to test it without the companion #42711)

@cmsbuild
Copy link
Contributor

-1

Failed Tests: UnitTests RelVals RelVals-INPUT AddOn
Summary: https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-5249f5/35760/summary.html
COMMIT: ca55839
CMSSW: CMSSW_14_0_X_2023-11-12-2300/el8_amd64_gcc12
User test area: For local testing, you can use /cvmfs/cms-ci.cern.ch/week1/cms-sw/cmssw/43226/35760/install.sh to create a dev area with all the needed externals and cmssw changes.

Unit Tests

I found 17 errors in the following unit tests:

---> test TestDQMOnlineClient-beamhlt_dqm_sourceclient had ERRORS
---> test TestDQMOnlineClient-beamhlt_dqm_sourceclient-legacy had ERRORS
---> test TestDQMOnlineClient-ctpps_dqm_sourceclient had ERRORS
and more ...

RelVals

----- Begin Fatal Exception 13-Nov-2023 10:57:47 CET-----------------------
An exception of category 'EventSetupConflict' occurred while
   [0] Calling beginJob
Exception Message:
two EventSetup Sources want to deliver type="TotemDAQMapping" label="TimingDiamond"
 from record TotemReadoutRcd. The two providers are 
1) type="PoolDBESSource" label="GlobalTag"
2) type="TotemDAQMappingESSourceXML" label="totemDAQMappingESSourceXML_TimingDiamond"
Please either
   remove one of these Sources
   or find a way of configuring one of them so it does not deliver this data
   or use an es_prefer statement in the configuration to choose one.
----- End Fatal Exception -------------------------------------------------
----- Begin Fatal Exception 13-Nov-2023 10:58:31 CET-----------------------
An exception of category 'EventSetupConflict' occurred while
   [0] Calling beginJob
Exception Message:
two EventSetup Sources want to deliver type="TotemDAQMapping" label="TimingDiamond"
 from record TotemReadoutRcd. The two providers are 
1) type="PoolDBESSource" label="GlobalTag"
2) type="TotemDAQMappingESSourceXML" label="totemDAQMappingESSourceXML_TimingDiamond"
Please either
   remove one of these Sources
   or find a way of configuring one of them so it does not deliver this data
   or use an es_prefer statement in the configuration to choose one.
----- End Fatal Exception -------------------------------------------------
----- Begin Fatal Exception 13-Nov-2023 10:58:36 CET-----------------------
An exception of category 'EventSetupConflict' occurred while
   [0] Calling beginJob
Exception Message:
two EventSetup Sources want to deliver type="TotemDAQMapping" label="TimingDiamond"
 from record TotemReadoutRcd. The two providers are 
1) type="PoolDBESSource" label="GlobalTag"
2) type="TotemDAQMappingESSourceXML" label="totemDAQMappingESSourceXML_TimingDiamond"
Please either
   remove one of these Sources
   or find a way of configuring one of them so it does not deliver this data
   or use an es_prefer statement in the configuration to choose one.
----- End Fatal Exception -------------------------------------------------
Expand to see more relval errors ...

RelVals-INPUT

  • 4.224.22_RunCosmics2011A/step2_RunCosmics2011A.log
  • 4.64.6_MinimumBias2010A/step2_MinimumBias2010A.log
  • 134.813134.813_RunCosmics2015C/step2_RunCosmics2015C.log
Expand to see more relval errors ...

AddOn Tests

----- Begin Fatal Exception 13-Nov-2023 10:59:25 CET-----------------------
An exception of category 'EventSetupConflict' occurred while
   [0] Calling beginJob
Exception Message:
two EventSetup Sources want to deliver type="TotemDAQMapping" label="TimingDiamond"
 from record TotemReadoutRcd. The two providers are 
1) type="PoolDBESSource" label="GlobalTag"
2) type="TotemDAQMappingESSourceXML" label="totemDAQMappingESSourceXML_TimingDiamond"
Please either
   remove one of these Sources
   or find a way of configuring one of them so it does not deliver this data
   or use an es_prefer statement in the configuration to choose one.
----- End Fatal Exception -------------------------------------------------
----- Begin Fatal Exception 13-Nov-2023 10:59:30 CET-----------------------
An exception of category 'EventSetupConflict' occurred while
   [0] Calling beginJob
Exception Message:
two EventSetup Sources want to deliver type="TotemDAQMapping" label="TimingDiamond"
 from record TotemReadoutRcd. The two providers are 
1) type="PoolDBESSource" label="GlobalTag"
2) type="TotemDAQMappingESSourceXML" label="totemDAQMappingESSourceXML_TimingDiamond"
Please either
   remove one of these Sources
   or find a way of configuring one of them so it does not deliver this data
   or use an es_prefer statement in the configuration to choose one.
----- End Fatal Exception -------------------------------------------------
----- Begin Fatal Exception 13-Nov-2023 10:59:34 CET-----------------------
An exception of category 'EventSetupConflict' occurred while
   [0] Calling beginJob
Exception Message:
two EventSetup Sources want to deliver type="TotemDAQMapping" label="TimingDiamond"
 from record TotemReadoutRcd. The two providers are 
1) type="PoolDBESSource" label="GlobalTag"
2) type="TotemDAQMappingESSourceXML" label="totemDAQMappingESSourceXML_TimingDiamond"
Please either
   remove one of these Sources
   or find a way of configuring one of them so it does not deliver this data
   or use an es_prefer statement in the configuration to choose one.
----- End Fatal Exception -------------------------------------------------
Expand to see more addon errors ...

@perrotta
Copy link
Contributor Author

please test with #42711

@cmsbuild
Copy link
Contributor

+1

Summary: https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-5249f5/35763/summary.html
COMMIT: ca55839
CMSSW: CMSSW_14_0_X_2023-11-13-1100/el8_amd64_gcc12
User test area: For local testing, you can use /cvmfs/cms-ci.cern.ch/week1/cms-sw/cmssw/43226/35763/install.sh to create a dev area with all the needed externals and cmssw changes.

Comparison Summary

Summary:

  • You potentially removed 69 lines from the logs
  • Reco comparison results: 174 differences found in the comparisons
  • DQMHistoTests: Total files compared: 50
  • DQMHistoTests: Total histograms compared: 3363028
  • DQMHistoTests: Total failures: 10
  • DQMHistoTests: Total nulls: 0
  • DQMHistoTests: Total successes: 3362996
  • DQMHistoTests: Total skipped: 22
  • DQMHistoTests: Total Missing objects: 0
  • DQMHistoSizes: Histogram memory added: 0.0 KiB( 49 files compared)
  • Checked 214 log files, 167 edm output root files, 50 DQM output files
  • TriggerResults: no differences found

@perrotta
Copy link
Contributor Author

perrotta commented Nov 13, 2023

+alca

@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. @rappoccio, @antoniovilela, @sextonkennedy (and backports should be raised in the release meeting by the corresponding L2)

@rappoccio
Copy link
Contributor

+1

@cmsbuild cmsbuild merged commit eacae5b into cms-sw:master Nov 17, 2023
@perrotta perrotta deleted the gtsForPpsDaqMapping branch November 18, 2023 06:56
# GlobalTag for Run2 data 2018B relvals only: HEM-15-16 fail
'run2_data_HEfail' : '133X_dataRun2_HEfail_v1',
'run2_data_HEfail' : '133X_dataRun2_HEfail_v2',
Copy link
Contributor Author

Choose a reason for hiding this comment

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

There was an error of mine while naming the updated DB: I wrote 133X_dataRun2_Hefail_v2 instead of 133X_dataRun2_HEfail_v2. This originates the error in the IBs for (e.g.) wf 136.8642.

I'm going to fix it in the DB, and there should be no need to fix the PR after that!

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Now 133X_dataRun2_HEfail_v2 exists in the IB, identical to 133X_dataRun2_Hefail_v2: https://cms-conddb.cern.ch/cmsDbBrowser/diff/Prod/gts/133X_dataRun2_Hefail_v2/133X_dataRun2_HEfail_v2

I expect that the IB error in 136.8642 will disappear while testing next CMSSW_14_0_X_2023-11-18-1100

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.

4 participants