-
Notifications
You must be signed in to change notification settings - Fork 4.6k
Run3-gex172 Update 2021 and 2023 scenarios with the corrected geometry for the GE21 demonstration chamber #43032
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
Conversation
…onstration chamber
|
+code-checks Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-43032/37209
|
|
A new Pull Request was created by @bsunanda (Sunanda Banerjee) for master. It involves the following packages:
@AdrianoDee, @mdhildreth, @cmsbuild, @Dr15Jones, @srimanob, @makortel, @bsunanda, @civanch can you please review it and eventually sign? Thanks. cms-bot commands are listed here |
|
@cmsbuild Please test |
|
+1 Summary: https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-c2770a/35215/summary.html Comparison SummarySummary:
|
|
No difference is seen because we use DB (GT) for Run-3, not XML. What is the plan for new GT? |
|
Shall make new payloads but I don't know how to make a Global Tag for that |
|
Anyway we need not backport this to 13_2 or lower |
|
+geometry |
@cms-sw/alca-l2 @cms-sw/upgrade-l2 |
|
+Upgrade No change is expected from this PR as we use DB, not XML. The report of this issue can be found here (See status of geometry presentation). |
|
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. @rappoccio, @sextonkennedy, @antoniovilela (and backports should be raised in the release meeting by the corresponding L2) |
Hi @bsunanda yes please provide the new payloads and we will take care of the GTs. |
|
+1
|
PR description:
Update 2021 and 2023 scenarios with the corrected geometry for the GE21 demonstration chamber
PR validation:
Use the runTheMatrix test workflows
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:
Nothing special