-
Notifications
You must be signed in to change notification settings - Fork 5
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
Fix cluster->TP matching for pixel tracking CPU workflow #111
Fix cluster->TP matching for pixel tracking CPU workflow #111
Conversation
|
Yes, |
@@ -716,6 +716,7 @@ def _uniqueFirstLayers(layerList): | |||
tpClusterProducerPixelTrackingOnly = tpClusterProducer.clone() | |||
# Need to use the modifier to customize because the exact EDProducer type depends on the modifier | |||
gpu.toModify(tpClusterProducerPixelTrackingOnly, src = "tpClusterProducerHeterogeneousPixelTrackingOnly") | |||
(~gpu).toModify(tpClusterProducerPixelTrackingOnly, pixelClusterSrc = "siPixelClustersPreSplitting") |
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.
mhm, this is above the level of ugliness that I would like to have...
can we set it to siPixelClustersPreSplitting
by default, and change it to something else for the gpu
case ?
Better now? (basically moving the |
I guess... though it took me few minutes to understand the changes. The reason you couldn't do |
So, users of |
Yes, exactly. This is the nasty side effect of applying (in #100 everybody is forced to clone/modify the CPU/GPU/whatever flavor modules explicitly) |
Yes. Even though if this model would be fully deployed, there would be only |
Validation summaryReference release CMSSW_10_2_0_pre6 at a674e1f
|
Fixes 10824.5 and 10824.7 . |
This detail got overlooked in #105.
@fwyzard @VinInn