DPL Analysis: use label+origin as binding for tables#14934
DPL Analysis: use label+origin as binding for tables#14934aalkin wants to merge 2 commits intoAliceO2Group:devfrom
Conversation
|
REQUEST FOR PRODUCTION RELEASES: This will add The following labels are available |
| } foo; | ||
| void process(aod::McCollision const&, soa::SmallGroups<soa::Join<aod::Collisions, aod::McCollisionLabels>> const&) {} | ||
| }; | ||
| };\ |
|
As discussed offline, it probably makes sense to introduce / extend the InputRecord API to get the objects by ConcreteDataMatcher rather than using the binding. This should be faster and reduce the complexity by removing the need for the label to be computed. |
|
Closing in favor of #14944 |
2 participants
Currently embedding workflows would not work as both inputs would have identical binding based on table label. Using label+origin as binding circumvents this problem.
@nzardosh