Skip to content

Making PatPV3D a Transformer instead of MulitTransformerFilter

Christoph Hasse requested to merge PatPV3DFutureNoFilter into master

Removing the filter functionality from PatPV3D.

This could mean a degradation of the throughput since an event with zero PVs which still has some VELO tracks will not be thrown away and thus cost time in following algorithms. I guess therefore we shouldn't quite yet merge this.

However, given @olupton's work in !1291 (merged) we could wait for that to be merged and add a similar filter? Or the other option would be a filter like the PrGECFilter given that the filter on PV's would also kill the whole Event and not provide a selection as the filters discussed in !1291 (merged) do. Hoping for some input on this.

fyi: @sstahl @cattanem

Edited by Marco Cattaneo

Merge request reports