-
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
Run3-hcx344 Try to fix the issue of Layer 0 weight in HCAL in the version 13_0_X - backport of #42083 #42092
Conversation
A new Pull Request was created by @bsunanda (Sunanda Banerjee) for CMSSW_13_0_X. It involves the following packages:
@civanch, @Dr15Jones, @makortel, @mdhildreth, @cmsbuild, @bsunanda can you please review it and eventually sign? Thanks. cms-bot commands are listed here
|
@cmsbuild Please test |
Pull request #42092 was updated. @civanch, @Dr15Jones, @makortel, @mdhildreth, @cmsbuild, @bsunanda can you please check and sign again. |
@cmsbuild Please test |
@cmsbuild Please test |
+1 Summary: https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-c90e95/33410/summary.html Comparison SummarySummary:
|
The question raised by Salavat in the master version of this PR should get answered before any possible backport |
The code in the repository is incomplete. So the new check in the ReLabellerCode for Layer0 weight is more complete and surely affects all multi-layer depth1 towers. It is a safer check and should be included in this release |
+geometry |
This pull request is fully signed and it will be integrated in one of the next CMSSW_13_0_X IBs (tests are also fine) and once validation in the development release cycle CMSSW_13_2_X is complete. This pull request will now be reviewed by the release team before it's merged. @perrotta, @dpiparo, @rappoccio (and backports should be raised in the release meeting by the corresponding L2) |
backport of #42083 |
+1
|
PR description:
Try to fix the issue of Layer 0 weight in HCAL in the version 13_0_X - backport of #42083
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:
backport of #42083 in the master