[14.0.X] Update Run3 HLT GT with PPS conditions for 2024 data-taking

[saumyaphor4252]

PR description:

Backport of #44035

The PR updates the Run3 HLT GT to include the PPS conditions needed prior-to/and complementary to the HLT menu updates being integrated and tested in https://its.cern.ch/jira/browse/CMSHLT-3030.

The updates in the GT are as follows:

• Replaces PPSOpticalFunctions_hlt_v9 --> PPSOpticalFunctions_hlt_v10
  • Additional IOV 2c2710a032f957718c87bcc41b44195b8a177bf9 from Run 362920 (2023-01-12)
• Includes new tags for LHCInfoPerFillRcd and LHCInfoPerLSRcd (Not yet in production, O2O not writing to these for now)
• Removal of old LHCInfo tag from HLT as a cleanup detailed in Remove "old" LHCInfo tag from Run3 GTs cms-AlCaDB/AlCaTools#87
• Replaces CTPPSRPAlignment_real_Run3_v2_hlt --> CTPPSRPAlignment_real_Run3_v4_hlt
  • Additional new IOVs starting Run 366396 (2023-04-21)

GT Difference

• run3_hlt
  https://cms-conddb.cern.ch/cmsDbBrowser/diff/Prod/gts/140X_dataRun3_HLT_frozen_v1/140X_dataRun3_HLT_frozen_v2

PR validation:

See master PR

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:

Verbatim backport of #44035

[cmsbuild]

A new Pull Request was created by @saumyaphor4252 for CMSSW_14_0_X.

It involves the following packages:

• Configuration/AlCa (alca)

@saumyaphor4252, @perrotta, @cmsbuild, @consuegs can you please review it and eventually sign? Thanks.
@yuanchao, @tocheng, @fabiocos, @mmusich, @rsreds, @Martin-Grunewald, @missirol 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

• Backported from Update Run3 HLT GT with PPS conditions for 2024 data-taking #44035

[cmsbuild]

cms-bot internal usage

[saumyaphor4252]

backport of #44035

[saumyaphor4252]

test parameters:

• workflows = 141.001,140.022,140.069,141.008,141.105,140.065,140.069,141.044

[saumyaphor4252]

test parameters:

• workflows = 141.001,140.022,140.069,141.008,141.105,140.065,140.069,141.044

[saumyaphor4252]

@cmsbuild please test

[cmsbuild]

+1

Summary: https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-0e60b0/37605/summary.html
COMMIT: 0a9edbc
CMSSW: CMSSW_14_0_X_2024-02-21-1100/el8_amd64_gcc12
User test area: For local testing, you can use /cvmfs/cms-ci.cern.ch/week1/cms-sw/cmssw/44045/37605/install.sh to create a dev area with all the needed externals and cmssw changes.

Comparison Summary

Summary:

• You potentially removed 11 lines from the logs
• Reco comparison results: 40 differences found in the comparisons
• DQMHistoTests: Total files compared: 54
• DQMHistoTests: Total histograms compared: 3668119
• DQMHistoTests: Total failures: 3
• DQMHistoTests: Total nulls: 0
• DQMHistoTests: Total successes: 3668094
• DQMHistoTests: Total skipped: 22
• DQMHistoTests: Total Missing objects: 0
• DQMHistoSizes: Histogram memory added: 0.0 KiB( 53 files compared)
• Checked 224 log files, 185 edm output root files, 54 DQM output files
• TriggerResults: no differences found

[perrotta]

+1

• Verbatim backport of Update Run3 HLT GT with PPS conditions for 2024 data-taking #44035, which is merged in master since CMSSW_14_1_X_2024-02-21-2300
• IB tests are failing for CMSSW_14_1_X_2024-02-21-2300: it is always painful to understand which could be the culprit when tenth of PRs are merged in the release at the same time, but looking at the output this one does not seem responsible of the failure (and similar ones were also present in some past IB, and therefore it is probably unrelated to all lastly merged PRs)

[cmsbuild]

This pull request is fully signed and it will be integrated in one of the next CMSSW_14_0_X IBs (tests are also fine) and once validation in the development release cycle CMSSW_14_1_X is complete. This pull request will now be reviewed by the release team before it's merged. @antoniovilela, @sextonkennedy, @rappoccio (and backports should be raised in the release meeting by the corresponding L2)

[mmusich]

urgent

• @cms-sw/orp-l2 please merge this PR, it's needed to let HLT menu development for 14_0_X (2/N) #44074 move on.

[rappoccio]

+1