-
Notifications
You must be signed in to change notification settings - Fork 4.4k
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-hgx336C Try to introduce the guard rings for both full and partial wafers of HGCal (will be a part of V18) #41048
Conversation
…HGCal (will be a part of V18)
-code-checks Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-41048/34614
Code check has found code style and quality issues which could be resolved by applying following patch(s)
|
+code-checks Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-41048/34616
|
A new Pull Request was created by @bsunanda (Sunanda Banerjee) for master. It involves the following packages:
@civanch, @Dr15Jones, @bsunanda, @makortel, @mdhildreth, @cmsbuild, @AdrianoDee, @srimanob can you please review it and eventually sign? Thanks. cms-bot commands are listed here |
@cmsbuild Please test |
-code-checks Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-41048/34619
Code check has found code style and quality issues which could be resolved by applying following patch(s)
|
+1 Summary: https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-6c34ee/31266/summary.html Comparison SummarySummary:
|
+1 geometry is changed, so Phase-2 WFs are affected. |
To confirm from the PR description, when you said it will be part of V18. But the PR touches v16, v17 by adding UseOffset which should not make the change in physics, but SIM history. So that why we see the difference in D88 in PR test. Do I understand correctly? |
@srimanob Yes it changes SIM history only and that is why we see some difference |
+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. @perrotta, @dpiparo, @rappoccio (and backports should be raised in the release meeting by the corresponding L2) |
+1 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I missed this one: I think this should be re-commented out, if we don't want to flood the outputs with these log messages. Could you please confirm, Sunanda?
@@ -8,7 +8,7 @@ | |||
#include "Geometry/HGCalCommonData/interface/HGCalGeometryMode.h" | |||
#include "Geometry/HGCalCommonData/interface/HGCalParameters.h" | |||
|
|||
//#define EDM_ML_DEBUG | |||
#define EDM_ML_DEBUG |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should this get re-commented out?
Ping @bsunanda |
{20, 14, 3, 4, 20}}; | ||
int np[6][5] = {{45, 39, 4, 5, 45}, | ||
{47, 40, 5, 0, 47}, | ||
{48, 41, 0, 1, 48}, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
PR description:
Try to introduce the guard rings for both full and partial wafers of HGCal (will be a part of V18).
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