-
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-trk10 Possible overlap removal in the T33 version of tracker geometry #42951
Conversation
+code-checks Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-42951/37097
|
A new Pull Request was created by @bsunanda (Sunanda Banerjee) for master. It involves the following packages:
@cmsbuild, @civanch, @Dr15Jones, @bsunanda, @makortel, @mdhildreth 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-d0e049/35052/summary.html Comparison SummarySummary:
|
@bsunanda , I would propose instead of given 2 choices propose MR with V1 variant, where "V1" is not included in the file name. This would be possible to merge. With time phase2 tracker experts may propose better solution on top. |
@civanch Once this PR is merged I can make V1 as the default till Tracker DPG thinks otherwise |
+geometry |
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) |
OK, agreed. |
+1 |
PR description:
Possible overlap removal in the T33 version of tracker geometry. Two possible ways of removing the overlap - (1) by reducing the length of ModuleDeadAreaFront|Back or by repositioning ModuleDeadAreaRight|Left. The final choice will be taken after consulting with Tracker DPG
PR validation:
Tested using the Geant4 Overlap testing tool
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