-
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
Phase2-hgx354C Make the XML files required for the V19 version of HGCal with a new longitudinal structure #44508
Conversation
…gitudinal structure
cms-bot internal usage |
+code-checks Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-44508/39624
|
A new Pull Request was created by @bsunanda for master. It involves the following packages:
@cmsbuild, @civanch, @bsunanda, @srimanob, @subirsarkar, @mdhildreth, @Dr15Jones, @makortel can you please review it and eventually sign? Thanks. cms-bot commands are listed here |
+geometry |
+1 Summary: https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-d079b0/38357/summary.html Comparison SummarySummary:
|
@srimanob Please approve this |
+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. @sextonkennedy, @antoniovilela, @rappoccio (and backports should be raised in the release meeting by the corresponding L2) |
+1 Summary: https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-d079b0/38431/summary.html Comparison SummarySummary:
|
+1 |
+1 Summary: https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-d079b0/38434/summary.html Comparison SummarySummary:
|
PR description:
Make the XML files required for the V19 version of HGCal with a new longitudinal structure
PR validation:
Put together by using the content of the flat file used in the V19 definition. The codes need to be modified and then a scenario can be built to make a full test
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