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
Generate 2021 Scenario Automatically #30214
Generate 2021 Scenario Automatically #30214
Conversation
The code-checks are being triggered in jenkins. |
+code-checks Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-30214/16079
|
A new Pull Request was created by @ianna (Ianna Osborne) for master. It involves the following packages: Configuration/Geometry @civanch, @Dr15Jones, @makortel, @cvuosalo, @ianna, @mdhildreth, @cmsbuild, @kpedro88 can you please review it and eventually sign? Thanks. cms-bot commands are listed here |
@ianna this is great. Since there are only some minor changes in generate2021Geometry.py compared to generate2026Geometry.py, maybe it's worth trying to unify these scripts? I can look at this if you want. Also, it might be nice to update Configuration/Geometry/README.md with info about the 2021 geometry. |
The code-checks are being triggered in jenkins. |
I'd appreciate if you take it from my hands. Thanks! |
@kpedro88 - also, if you'd like to keep "D" in the file name, there will be wide-spread changes in configurations across the whole CMSSW :-( |
We can make the "D" depend on the 2021 vs. 2026 settings. |
+code-checks Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-30214/16083
|
Indeed, part of my motivation is to be able to reuse the 2021 dd4hep setup for 2026 |
Pull request #30214 was updated. @civanch, @Dr15Jones, @makortel, @cvuosalo, @ianna, @mdhildreth, @cmsbuild, @kpedro88 can you please check and sign again. |
@cmsbuild please test |
+code-checks Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-30214/16144
|
Pull request #30214 was updated. @civanch, @Dr15Jones, @makortel, @cvuosalo, @ianna, @mdhildreth, @cmsbuild, @kpedro88 can you please check and sign again. |
@ianna if the purpose is to generate a DD4hep full configuration, the |
please test |
The tests are being triggered in jenkins.
|
+1 |
Comparison job queued. |
Comparison is ready Comparison Summary:
|
+1 |
+upgrade |
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:
Similar to 2026 scenarios, 2021 scenario is autogenerated by a script.
@fabiocos , could you, please, check if eras and modifies are correctly defined
produce a dd4hep 2021 scenario from the same script
add PPS in the CTPPS section
add automated validation to check if the 2021 scenario was modified by hand
PR validation:
if this PR is a backport please specify the original PR and why you need to backport that PR:
Before submitting your pull requests, make sure you followed this checklist: