-
Notifications
You must be signed in to change notification settings - Fork 4.3k
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
Update HLT GT with ECAL DQM tower and channel status tags #38455
Conversation
+code-checks Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-38455/30667
|
A new Pull Request was created by @malbouis for master. It involves the following packages:
@cmsbuild, @malbouis, @tvami, @yuanchao, @francescobrivio can you please review it and eventually sign? Thanks. cms-bot commands are listed here |
please test |
type ecal |
+1 Summary: https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-62dca0/25670/summary.html Comparison SummarySummary:
|
+alca
|
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. @perrotta, @dpiparo, @qliphy (and backports should be raised in the release meeting by the corresponding L2) |
+1 |
PR description:
This PR is mainly to include Ecal DQM channel and tower status in the HLT (and HLT_relval) GTs, needed in PR #38357 + backports.
The Ecal tags to be included in HLT GT are:
EcalDQMChannelStatus_v1_hlt
andEcalDQMTowerStatus_v1_hlt
.We also take the chance to include the PPS optical function tag, that had already been included in the Express and Prompt GTs for P5 operations:
PPSOpticalFunctions_hlt_v9
All three tags were include in HLT and HLT_relval GTs.
The differences wrt to the previous GTs are shown below:
run3_hlt
https://cms-conddb.cern.ch/cmsDbBrowser/diff/Prod/gts/124X_dataRun3_HLT_frozen_v2/124X_dataRun3_HLT_frozen_v3
run3_hlt_relval
https://cms-conddb.cern.ch/cmsDbBrowser/diff/Prod/gts/124X_dataRun3_HLT_relval_v3/124X_dataRun3_HLT_relval_v5
We also took care that there are no differences other than the L1 menus between the frozen and relval GTs:
https://cms-conddb.cern.ch/cmsDbBrowser/diff/Prod/gts/124X_dataRun3_HLT_relval_v5/124X_dataRun3_HLT_frozen_v3
PR validation:
nohup runTheMatrix.py -l 139.001 --ibeos -j16
if this PR is a backport please specify the original PR and why you need to backport that PR:
This is not a backport but will be backported to 124X and 123X.