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 support for L1T EtSums of type kZDC{P,M} as trigger objects at HLT #42707

Merged
merged 1 commit into from
Sep 4, 2023

Conversation

missirol
Copy link
Contributor

@missirol missirol commented Sep 2, 2023

PR description:

This PR adds support for L1T EtSums of type kZDC{P,M} as trigger objects at HLT. These new types were introduced in #42634 (L1T-ZDC emulation).

Two types, trigger::TriggerL1ZDC{P,M}, are added to TriggerTypeDefs.h, and support for them is added to the plugin HLTL1TSeed (which puts L1T objects into the edm::Event as part of the TriggerFilterObjectWithRefs data format).

A similar update was done in #36951 to support the L1T data formats for "MuonShowers". One difference in this PR is that the underlying data format, i.e. l1t::EtSum, is not a new one (unlike l1t::MuonShower was), and this makes the changes on the HLT side less extensive compared to #36951.

Note: the edm::InputTag added to HLTL1TSeed in this PR will point to a non-existing collection in the current HLT menus until an unpacker for the ZDC inputs to the L1T-uGT is added to CMSSW (see #42634 (comment)). For this reason, only a LogDebug message is issued when this collection is missing, and eventually this should be replaced by a edm::LogWarning (once the unpacker is available).

No changes expected.

PR validation:

addOnTests.py passed.

If this PR is a backport, please specify the original PR and why you need to backport that PR. If this PR will be backported, please specify to which release cycle the backport is meant for:

CMSSW_13_2_X

@cmsbuild
Copy link
Contributor

cmsbuild commented Sep 2, 2023

+code-checks

Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-42707/36800

  • This PR adds an extra 28KB to repository

@cmsbuild
Copy link
Contributor

cmsbuild commented Sep 2, 2023

A new Pull Request was created by @missirol (Marino Missiroli) for master.

It involves the following packages:

  • DataFormats/HLTReco (hlt)
  • HLTrigger/HLTfilters (hlt)

@cmsbuild, @missirol, @mmusich, @Martin-Grunewald can you please review it and eventually sign? Thanks.
@Martin-Grunewald, @silviodonato, @rovere this is something you requested to watch as well.
@rappoccio, @antoniovilela, @sextonkennedy you are the release manager for this.

cms-bot commands are listed here

@missirol
Copy link
Contributor Author

missirol commented Sep 2, 2023

urgent

Because of #42708 (comment).

@cmsbuild cmsbuild added the urgent label Sep 2, 2023
@missirol
Copy link
Contributor Author

missirol commented Sep 2, 2023

please test

@cmsbuild
Copy link
Contributor

cmsbuild commented Sep 2, 2023

+1

Summary: https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-b0de4f/34585/summary.html
COMMIT: 8503a89
CMSSW: CMSSW_13_3_X_2023-09-01-2300/el8_amd64_gcc11
User test area: For local testing, you can use /cvmfs/cms-ci.cern.ch/week0/cms-sw/cmssw/42707/34585/install.sh to create a dev area with all the needed externals and cmssw changes.

Comparison Summary

Summary:

  • You potentially removed 164 lines from the logs
  • Reco comparison results: 356 differences found in the comparisons
  • DQMHistoTests: Total files compared: 48
  • DQMHistoTests: Total histograms compared: 3153350
  • DQMHistoTests: Total failures: 346
  • DQMHistoTests: Total nulls: 0
  • DQMHistoTests: Total successes: 3152982
  • DQMHistoTests: Total skipped: 22
  • DQMHistoTests: Total Missing objects: 0
  • DQMHistoSizes: Histogram memory added: 0.0 KiB( 47 files compared)
  • Checked 207 log files, 159 edm output root files, 48 DQM output files
  • TriggerResults: no differences found

@missirol
Copy link
Contributor Author

missirol commented Sep 2, 2023

You potentially removed 164 lines from the logs
Reco comparison results: 356 differences found in the comparisons

The DQM differences in the outputs of PR tests seem compatible with #39803, #39754 and #42525.

I will relaunch the tests (now with a different IB as baseline) to verify that there are no DQM differences due to this PR.

@missirol
Copy link
Contributor Author

missirol commented Sep 2, 2023

please test

@cmsbuild
Copy link
Contributor

cmsbuild commented Sep 2, 2023

+1

Summary: https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-b0de4f/34586/summary.html
COMMIT: 8503a89
CMSSW: CMSSW_13_3_X_2023-09-02-1100/el8_amd64_gcc11
User test area: For local testing, you can use /cvmfs/cms-ci.cern.ch/week0/cms-sw/cmssw/42707/34586/install.sh to create a dev area with all the needed externals and cmssw changes.

Comparison Summary

Summary:

  • You potentially added 26 lines to the logs
  • Reco comparison results: 11 differences found in the comparisons
  • DQMHistoTests: Total files compared: 48
  • DQMHistoTests: Total histograms compared: 3153350
  • DQMHistoTests: Total failures: 6
  • DQMHistoTests: Total nulls: 0
  • DQMHistoTests: Total successes: 3153322
  • DQMHistoTests: Total skipped: 22
  • DQMHistoTests: Total Missing objects: 0
  • DQMHistoSizes: Histogram memory added: 0.0 KiB( 47 files compared)
  • Checked 207 log files, 159 edm output root files, 48 DQM output files
  • TriggerResults: no differences found

@missirol
Copy link
Contributor Author

missirol commented Sep 3, 2023

No DQM differences due to this PR in the latest round of tests, as expected.

@@ -104,6 +107,7 @@ void HLTL1TSeed::fillDescriptions(edm::ConfigurationDescriptions& descriptions)
desc.add<edm::InputTag>("L1JetInputTag", edm::InputTag("hltGtStage2Digis:Jet"));
desc.add<edm::InputTag>("L1TauInputTag", edm::InputTag("hltGtStage2Digis:Tau"));
desc.add<edm::InputTag>("L1EtSumInputTag", edm::InputTag("hltGtStage2Digis:EtSum"));
desc.add<edm::InputTag>("L1EtSumZdcInputTag", edm::InputTag("hltGtStage2Digis:EtSumZDC"));
Copy link
Contributor

Choose a reason for hiding this comment

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

Let's hope L1T is using that label.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

For L1EtSumZdcInputTag, I kept Zdc as in the parameters of L1TGlobalProducer (#42634). And yes, for :EtSumZDC I plan to ask that they use this name when they update L1TRawToDigi (unpacker).

@Martin-Grunewald
Copy link
Contributor

+1

@cmsbuild
Copy link
Contributor

cmsbuild commented Sep 4, 2023

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)

@antoniovilela
Copy link
Contributor

+1

@cmsbuild cmsbuild merged commit 5b4fe36 into cms-sw:master Sep 4, 2023
1 check passed
@missirol missirol deleted the devel_hltL1TSeedEtSumZDC branch September 4, 2023 16:23
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