-
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
Duplication of clusterizers for bricked pixels #35519
Comments
assign reconstruction |
A new Issue was created by @jpata Joosep Pata. @Dr15Jones, @perrotta, @dpiparo, @makortel, @smuzaffar, @qliphy can you please review it and eventually sign/assign? Thanks. cms-bot commands are listed here |
@franzglessgen can you let us know if there's any update on this? Are the studies concluded? |
Hi ! I do not think the studies are over yet, @emiglior might be more up to date about the latest development. |
Studies on Tracker geometries featuring bricked pixels are not done yet (ETA: end of January 2022) |
a kind ping on this issue. |
@franzglessgen @emiglior a kind ping on this issue |
Hi Josep, indeed the bricked pixel option is currently disfavored. We will have the final decision (and therefore the clean up of the code) in 1 month. |
type trk |
@emiglior @franzglessgen kind ping on this. |
@emiglior @franzglessgen any news? |
The last bricked pixel geometry in cmssw is removed at #38061. |
Indeed the plan is to drop the special local reco for bricked pixels The question is if removing the classes below is enough or if you want to revert changes in the base classes as well Few examples:
|
@jpata @cms-sw/reconstruction-l2 can you give your opinion on #35519 (comment) |
The changes introduced in #35441 that only support the bricked pixels and won't be tested/used/supported in the future should be removed. Changes that were introduced in that PR that generally support code reuse in pixel local reco could stay. |
I would say so, but I don't have an overview in front of me now, so you can exercise some judgement. My main point was that code that becomes unused and thus untested should be removed. Thanks for taking care of this! |
@franzglessgen yes, you have to wait that PR#38061 is merged |
now that #38061 is merged, can we remove the duplicated code? |
Thanks for the notification, I am going on holiday this week so I'll start to clean up the code mid July if that's okay. |
@franzglessgen please note #38529 |
Oh it has been done already, thanks for the info! |
+reconstruction |
This issue is fully signed and ready to be closed. |
Hi!
Thanks for the ping. I am not aware of the latest status but if I get the
green light by Ernesto I could remove this piece of code.
Cheers,
Franz
Le jeu. 12 mai 2022 à 16:01, Joosep Pata ***@***.***> a
écrit :
… @emiglior <https://github.com/emiglior> @franzglessgen
<https://github.com/franzglessgen> any news?
—
Reply to this email directly, view it on GitHub
<#35519 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ANU4VI6I3GERMYROUDTKWK3VJUFNNANCNFSM5FIUOBXQ>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
The following files were duplicated with minor modifications in #35441.
Per the comments #35441 (comment), the duplication should be reviewed as soon as the studies with bricked pixels are done, and subsequently removed from the codebase (or otherwise rewritten to avoid duplication).
The text was updated successfully, but these errors were encountered: