-
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-hgx323 Further correction for ring number assignment of scintillator hits in HGCal geometry versions beyond V13 #39164
Conversation
… HGCal geometry versions V16 and V17
-code-checks Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-39164/31749
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-39164/31750
|
A new Pull Request was created by @bsunanda (Sunanda Banerjee) for master. It involves the following packages:
@civanch, @Dr15Jones, @bsunanda, @makortel, @ianna, @mdhildreth, @cmsbuild, @AdrianoDee, @srimanob 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-9f1384/27040/summary.html Comparison SummarySummary:
|
type bug-fix |
Hi @bsunanda
Thanks. |
This bug was there all the time. When the position at the border of 2 rings, it is usually referred to as the lower ring number. This is fine as long as there is no tile in the lower ring. We did not have a good valid test of a detid earlier. We have to introduce one now and that revealed the discrepancy. We do have detailed testing code in the repository and we do conduct them to look into details. The standard validation code can look into broad discrepancies so far and the detailed tests are better done by the experts of the geometry code. |
+1 |
+Upgrade The fix should be followed up in validation. |
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, @qliphy, @rappoccio (and backports should be raised in the release meeting by the corresponding L2) |
(iphi <= hgpar_->scintCells(layer))); | ||
bool ok = ((irad >= hgpar_->iradMinBH_[indx.first]) && (irad <= (hgpar_->iradMaxBH_[indx.first] + 1)) && (iphi > 0) && | ||
(iphi <= hgpar_->scintCells(layer))); | ||
return ((ok && trapezoidFile()) ? tileExist(zside, layer, irad, iphi) : ok); |
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.
To be correct, it should be
return ((ok && trapezoidFile()) ? tileExist(zside, layer, irad, iphi) : ok); | |
return ((ok && trapezoidFile()) ? tileExist(zside, layer, irad, iphi) : true); |
(even if by now the net result is the same)
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 don't think your correction is right - irrespective of trapezoidFile() the earlier test is good for all types of scintillators
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 don't think your correction is right - irrespective of trapezoidFile() the earlier test is good for all types of scintillators
I understand that in practice ok && ok
is identical to ok && true
. But translating in C++ the sentence "irrespective of trapezoidFile() the earlier test is good for all types of scintillators" is exactly ok && true
+1
|
By the way, I see failure in Static Check build log, Sorry that I miss to look on it when approved the PR. |
Hmm ... D77 is not expected for the change. There is nothing in PR mentioned about the effect on old geometry. I think this question should be answered first. I am very sorry to miss this when review. I mostly focused on D88 in private production and forget to look on PR test result. |
Indeed @srimanob , we were too quick Let revert this, so that it won't pollute pre5: #39198 @bsunanda please redo the PR, and fix it by taking #39164 (comment) and #39164 (comment) into account (and also #39164 (review)) |
D77 is expected for the change - I mentioned V16 and V17 because they are to be kept for future. It will certainly affect V14 and V15 as well. D77 is V14 |
Please do not revert it. The static errors in topology is for debug. I shall take care of that as well as for HCAL stuff separately. |
Hi @bsunanda |
Why a new PR with the same content - cannot be this one restored back?
…________________________________
From: Phat Srimanobhas ***@***.***
Sent: 26 August 2022 04:30
To: cms-sw/cmssw
Cc: Sunanda Banerjee; Mention
Subject: Re: [cms-sw/cmssw] Phase2-hgx323 Further correction for ring number assignment of scintillator hits in HGCal geometry versions beyond V13 (PR #39164)
Hi @bsunanda<https://github.com/bsunanda>
Thanks for clarification. Please open the new PR.
—
Reply to this email directly, view it on GitHub<#39164 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/ABGMZOVEU5QARQQUWQU6NR3V3AT5VANCNFSM57NZOHTQ>.
You are receiving this because you were mentioned.Message ID: ***@***.***>
|
I leave the technical part to @cms-sw/orp-l2 since this PR is merged already. I don't know if it is possible to do. |
PR description:
Further correction for ring number assignment of scintillator hits in HGCal geometry versions V14, V15, V16 and V17
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:
This is a bug fix for all versions of HGCal geometry