-
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
Remove Phase-2 IT bricked design #40443
Conversation
+code-checks Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-40443/33592
|
A new Pull Request was created by @tvami (Tamas Vami) for master. It involves the following packages:
@malbouis, @civanch, @clacaputo, @cmsbuild, @AdrianoDee, @srimanob, @saumyaphor4252, @mdhildreth, @ggovi, @tvami, @mandrenguyen, @francescobrivio 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-d435b4/29821/summary.html Comparison SummarySummary:
|
hold
|
Pull request has been put on hold by @mmusich |
It was discussed with Ernesto, I added you to the email thread now |
thanks. Supporting storage for the bricked pixel information entailed much more involved changes in the base tracker geometry classes layouts than what is removed here (see b462e3b). I am wondering if one should try to address that first is there is really no usage for bricked-ness simulation at any level. |
Perhaps I am misunderstanding your point: Do you mean remove all the occurrences of "isBricked()" (and similar) or also the include of the header files (e.g. PTrackerAdditionalParametersPerDetRcd.h) through which the brickedness was implemented? Meanwhile, I will cross check again with people working on ph-3 about their actual plans on bricked pixels. |
yes, carrying around this additional complication for no apparent reason doesn't not seem very sustainable for maintenance reasons in the long run. |
I can do another commit which will remove bricked from the topology, but only later today |
So there is an |
That's necessary because |
@mmusich , |
+reconstruction |
@smuzaffar hmm, would |
yes |
+upgrade |
I was reading the thread: is it there at the end something that documents this decision? |
Did phase-3 people get back to you about it? |
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) |
I guess it will be discussed today at the ph2 tracker simulation meeting |
I see , thanks! |
please go on with the removal |
hi @cms-sw/orp-l2 can we merge this soon, before I'll need to rebase again? Thanks! |
+1
|
@tvami a unit test failure in the IBs shows that there is a remaining inclusion of TrackerAdditionalParametersPerDet_cfi.py in DQM/SiStripCommon/test/testTkHistoMap_cfg.py: could you please have a look? |
ok, I'm on it |
PR description:
PixelBrickedDigitizerAlgorithm
since that design was discardedgeneric_position_formula_y_bricked
which seems to have been a remnant from the cleanup from the local reconamespace
naming to obey rule 2.7PR validation:
20834.0
to make sure the default Ph2 digitizer worksIf 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:
Not a backport, and no backport needed