-
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 tracker alignment for 2021 realistic scenario #27651
Update tracker alignment for 2021 realistic scenario #27651
Conversation
A new Pull Request was created by @christopheralanwest for CMSSW_10_6_X. It involves the following packages: Configuration/AlCa @christopheralanwest, @tocheng, @cmsbuild, @franzoni, @tlampen, @pohsun can you please review it and eventually sign? Thanks. cms-bot commands are listed here |
please test |
The tests are being triggered in jenkins. |
Comparison job queued. |
Comparison is ready Comparison Summary:
|
+1
|
This pull request is fully signed and it will be integrated in one of the next CMSSW_10_6_X IBs (tests are also fine) and once validation in the development release cycle CMSSW_11_0_X is complete. This pull request will now be reviewed by the release team before it's merged. @davidlange6, @slava77, @smuzaffar, @fabiocos (and backports should be raised in the release meeting by the corresponding L2) |
+1 |
PR description:
The global tag queues for the
phase1_2021_realistic
scenario had to be branched to support the different needs of the Run-3 LHCC studies and CMSSW development. This PR introduces an updated tracker alignment [1] and a purely technical payload [2]. It re-synchronizesauto:phase1_2021_realistic
with the GT used for the Run-3 studies,106X_mcRun3_2021_realistic_v3
.It would be useful to have this PR merged to avoid spurious differences in comparison tests in future PRs that affect
phase1_2021_realistic
conditions, for example, the eventual 10_6_X backport of #27644.GT diff with respect to current autoCond:
https://cms-conddb.cern.ch/cmsDbBrowser/diff/Prod/gts/106X_upgrade2021_realistic_v8/106X_upgrade2021_realistic_v9
GT diff with respect to GT for Run-3 studies:
https://cms-conddb.cern.ch/cmsDbBrowser/diff/Prod/gts/106X_mcRun3_2021_realistic_v3/106X_upgrade2021_realistic_v9
The tag difference above corresponds to payloads that were introduced by PR #27203 and ignored for Run-3 scenarios in a subsequent commit to that PR.
[1] https://indico.cern.ch/event/831067/contributions/3485251/attachments/1871918/3080764/Run3Alignment_AlcaDB017_AdeWit.pdf
[2] https://cms-conddb.cern.ch/cmsDbBrowser/diff/Prod/gts/106X_upgrade2021_realistic_v8/106X_upgrade2021_realistic_v9
PR validation:
Payload validation can be found in [1] and [2]. In addition,
runTheMatrix.py -l 11624.0
was executed as a technical test.[1] https://indico.cern.ch/event/831067/contributions/3485251/attachments/1871918/3080764/Run3Alignment_AlcaDB017_AdeWit.pdf
[2] https://cms-conddb.cern.ch/cmsDbBrowser/diff/Prod/gts/106X_upgrade2021_realistic_v8/106X_upgrade2021_realistic_v9
if this PR is a backport please specify the original PR:
This is not a backport per se but PR #27441 introduced into 11_0_X the tracker alignment payload used in this PR. But it introduced other changes as well; only the changes needed for consistency with existing 10_6_X workflows are used here.