-
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 PPS records for 2018 and Run-3 #30890
Update PPS records for 2018 and Run-3 #30890
Conversation
The code-checks are being triggered in jenkins. |
test parameters |
+code-checks Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-30890/17276
|
A new Pull Request was created by @christopheralanwest for master. It involves the following packages: Configuration/AlCa @cmsbuild, @pohsun, @christopheralanwest, @tocheng, @tlampen can you please review it and eventually sign? Thanks. cms-bot commands are listed here |
please test |
The tests are being triggered in jenkins.
|
+1 |
Comparison job queued. |
Comparison is ready @slava77 comparisons for the following workflows were not done due to missing matrix map:
Comparison Summary:
|
+1
|
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. @silviodonato, @dpiparo (and backports should be raised in the release meeting by the corresponding L2) |
+1 |
PR description:
This PR is a technical update to include three PPS tags in 2018 and Run-3 GTs:
CTPPSPixelAnalysisMask_v1_mc
CTPPSPixelDAQMapping_v1_mc
CTPPSPixelGainCalibrations_v1_mc
For 2018 GTs, this replaces the same tags but without the "_v1" string in the tag name. For Run-3 GTs, no
CTPPSPixelAnalysisMaskRcd
,CTPPSPixelDAQMappingRcd
orCTPPSPixelGainCalibrationsRcd
records were previously present in the GT. The absence of these records causes spurious issues when testing PPS simulation pull requests.In addition, an obsolete unlabeled
SiPixel2DTemplateDBObjectRcd
is removed from theauto:phase1_2018_realistic_hi
GT.No changes are expected in any workflow as the PPS simulation is not yet present.
The GT diffs are as follows:
2018 design
https://cms-conddb.cern.ch/cmsDbBrowser/diff/Prod/gts/111X_upgrade2018_design_v1/112X_upgrade2018_design_v1
2018 realistic
https://cms-conddb.cern.ch/cmsDbBrowser/diff/Prod/gts/112X_upgrade2018_realistic_v1/112X_upgrade2018_realistic_v2
2018 heavy ion
https://cms-conddb.cern.ch/cmsDbBrowser/diff/Prod/gts/110X_upgrade2018_realistic_HI_v5/112X_upgrade2018_realistic_HI_v1
2018 realistic (HE fail)
https://cms-conddb.cern.ch/cmsDbBrowser/diff/Prod/gts/112X_upgrade2018_realistic_HEfail_v1/112X_upgrade2018_realistic_HEfail_v2
2018 cosmics (tracker deco mode)
https://cms-conddb.cern.ch/cmsDbBrowser/diff/Prod/gts/112X_upgrade2018cosmics_realistic_deco_v1/112X_upgrade2018cosmics_realistic_deco_v2
2018 cosmics (tracker peak mode)
https://cms-conddb.cern.ch/cmsDbBrowser/diff/Prod/gts/112X_upgrade2018cosmics_realistic_peak_v1/112X_upgrade2018cosmics_realistic_peak_v2
2021 design
https://cms-conddb.cern.ch/cmsDbBrowser/diff/Prod/gts/112X_mcRun3_2021_design_v3/112X_mcRun3_2021_design_v4
2021 realistic
https://cms-conddb.cern.ch/cmsDbBrowser/diff/Prod/gts/112X_mcRun3_2021_realistic_v3/112X_mcRun3_2021_realistic_v4
2021 cosmics
https://cms-conddb.cern.ch/cmsDbBrowser/diff/Prod/gts/112X_mcRun3_2021cosmics_realistic_deco_v3/112X_mcRun3_2021cosmics_realistic_deco_v4
2021 heavy ion
https://cms-conddb.cern.ch/cmsDbBrowser/diff/Prod/gts/112X_mcRun3_2021_realistic_HI_v3/112X_mcRun3_2021_realistic_HI_v4
2023 realistic
https://cms-conddb.cern.ch/cmsDbBrowser/diff/Prod/gts/112X_mcRun3_2023_realistic_v3/112X_mcRun3_2023_realistic_v4
2024 realistic
https://cms-conddb.cern.ch/cmsDbBrowser/diff/Prod/gts/112X_mcRun3_2024_realistic_v3/112X_mcRun3_2024_realistic_v4
PR validation:
The new PPS payloads have already been used in the offline data GT since 2018.
In addition, a technical test was performed:
runTheMatrix.py -l limited,12024.0,7.23,159.0,12834.0,11224.0,11024.2,7.4 --ibeos
if this PR is a backport please specify the original PR and why you need to backport that PR:
This PR is not a backport and should not be backported.