HLT menu development for 14_1_X (2/N) [14_2_X]

[mmusich]

PR description:

Development of HLT menus for CMSSW_14_1_X (branch CMSSW_14_2_X):

• This is the PR for the master branch, which will then be backported down to 14_1_X (the latter is the release cycle currently used for Run-3 HLT-menu development).

These updates correspond to the changes accumulated in the 14_1_X release cycle for the "PRef V1.0" menu: first menu for the 2024 pp reference data-taking period.

This update includes the integration of the following changes:

• migration of the combined HLT table and related subtables to CMSSW_14_1_1

In addition we include the integration of the following JIRA tickets:

• CMSHLT-3325 [HIN] Forward/UPC Triggers request for pp Reference Run 2024
• CMSHLT-3338 [HIN] Muon Triggers for PbPb Run 2024
• CMSHLT-3340 [HIN] Jet Triggers for pp Reference Run 2024
• CMSHLT-3343 [HIN] E/gamma Triggers for pp Reference Run 2024
• CMSHLT-3345 [HIN] Remove PPRefExotica PD/stream and re-assign paths to PPRefSingleMuon
• CMSHLT-3346 [HIN] Justify Commissioning{ZDC,RawPrime} PDs in the PRef menu
• CMSHLT-3348 [HIN] Add two seeds to hltL1sUPCHFafterglowCombined
• CMSHLT-3350 [HIN] Forward/UPC Triggers request for PbPb Run 2024
• CMSHLT-3356 [HIN] E/gamma Triggers for PbPb Run 2024
• CMSHLT-3357 [TSG] Release of special menus V1.6 (for PRef, HIon runs)
• CMSHLT-3363 [HIN,TSG] Sync offline menu with the 2023 PRef online menu

In this PR we also have the following commits:

• 3da4904 update of L1T HIon menu in TSG GTs to L1Menu_CollisionsHeavyIons2024_v1_0_5_xml
• 0a490e2 Finalize integration of the following tickets
  • CMSHLT-3310 [TSG] update input files for TSG tests to more modern datasets (2024)
• 0880f31 Update hltPathOwners.json including paths for menus PRef 2024 V1.0 and HIon 2024 V1.0
• d07ff79 Bumped version of Paths for HLT PRef-2024 V1.0

PR validation:

TSG Integration tests.

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:

Not a backport, but it will be backported to CMSSW_14_1_X.

[cmsbuild]

cms-bot internal usage

[mmusich]

type hlt-integration

[cmsbuild]

+code-checks

Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-46375/42220

[cmsbuild]

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

It involves the following packages:

• Configuration/HLT (hlt)
• HLTrigger/Configuration (hlt)

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

cms-bot commands are listed here

[mmusich]

enable gpu

[mmusich]

@cmsbuild, please test

[cmsbuild]

+1

Size: This PR adds an extra 912KB to repository
Summary: https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-ed9f34/42174/summary.html
COMMIT: d07ff79
CMSSW: CMSSW_14_2_X_2024-10-14-1100/el8_amd64_gcc12
Additional Tests: GPU
User test area: For local testing, you can use /cvmfs/cms-ci.cern.ch/week1/cms-sw/cmssw/46375/42174/install.sh to create a dev area with all the needed externals and cmssw changes.

Comparison Summary

Summary:

• You potentially added 3 lines to the logs
• Reco comparison results: 124 differences found in the comparisons
• DQMHistoTests: Total files compared: 44
• DQMHistoTests: Total histograms compared: 3317791
• DQMHistoTests: Total failures: 4673
• DQMHistoTests: Total nulls: 0
• DQMHistoTests: Total successes: 3313098
• DQMHistoTests: Total skipped: 20
• DQMHistoTests: Total Missing objects: 0
• DQMHistoSizes: Histogram memory added: 0.728 KiB( 43 files compared)
• DQMHistoSizes: changed ( 12834.0,... ): 0.104 KiB HLT/Filters
• Checked 193 log files, 163 edm output root files, 44 DQM output files
• TriggerResults: no differences found

GPU Comparison Summary

Summary:

• No significant changes to the logs found
• Reco comparison results: 0 differences found in the comparisons
• DQMHistoTests: Total files compared: 7
• DQMHistoTests: Total histograms compared: 53015
• DQMHistoTests: Total failures: 25
• DQMHistoTests: Total nulls: 0
• DQMHistoTests: Total successes: 52990
• DQMHistoTests: Total skipped: 0
• DQMHistoTests: Total Missing objects: 0
• DQMHistoSizes: Histogram memory added: 0.0 KiB( 6 files compared)
• Checked 24 log files, 30 edm output root files, 7 DQM output files
• TriggerResults: no differences found

[mmusich]

+hlt

• changes in the HLTFilters DQM folders are due the path versioning (d07ff79).

[cmsbuild]

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

[mandrenguyen]

+1

[smuzaffar]

@mmusich , some workflows in the IBs are failing with error [a] . Could it be due to this Pr changes?

[a] https://cmssdt.cern.ch/SDT/cgi-bin/logreader/el8_amd64_gcc12/CMSSW_14_2_X_2024-10-15-1100/pyRelValMatrixLogs/run/160.0_HydjetQ_B12_5362GeV_2023_ppReco/step2_HydjetQ_B12_5362GeV_2023_ppReco.log#/625-625

----- Begin Fatal Exception 15-Oct-2024 13:47:04 CEST-----------------------
An exception of category 'FailModule' occurred while
   [0] Processing  Event run: 1 lumi: 1 event: 1 stream: 0
   [1] Running path 'HLT_HIL2SingleMu0_Centrality40to100_v1'
   [2] Calling method for module HLTL1TSeed/'hltL1sSingleMu0Centrality40to100BptxAND'
Exception Message:

Algorithm L1_SingleMu0_Centrality_40_100_BptxAND, requested as seed by a HLT path, cannot be matched to a L1 algo name in any GlobalObjectMap
Please check if algorithm L1_SingleMu0_Centrality_40_100_BptxAND is present in the L1 menu

----- End Fatal Exception -------------------------------------------------

[mmusich]

@smuzaffar

Could it be due to this Pr changes?

yes, but it's already solved by #46379

[mmusich]

yes, but it's already solved by #46379

that PR solves part of the issues, but not everything, #46398 addresses the rest