Adding function to return a list of filters and tupling algorithms

added DPA-WP3 label

assigned to @dfazzini

added 1 commit

6ef5a02e - Fixed formatting

Compare with previous version

added 1 commit

82c6daf0 - add 'ConfiguredFuntuple' function and related qmtest

Compare with previous version

added 2 commits

f41c97c4 - Fixed formatting
42fa806f - Fixed linting

Compare with previous version

changed the description

marked this merge request as ready

changed title from Draft: function to return a list of DV algorithms to Adding function to return a list of filters and tupling algorithms

requested review from @erodrigu and @pkoppenb

changed the description

added new feature label

Looks nice. Does this handle cases as !569 (merged) where FunTuple has a dependency on DecayTreeFitterAlg ?

Since you pinged me as a reviewer - I have to say that I'm not convinced by the need for this wrapper that will only typically add a filter when instantiating FunTuple. And many users won't need filters either, I imagine. I know that you are going to say we should avoid having every user adding boilerplate business to their scripts but this one seems like something you would want the user to be clear about. This here reminds me of all the configuredXXX helpers for tracking; there it was most probably necessary because many things needed to be done "behind the scenes" correctly. I don't see a big benefit here.

One point that is particularly ugly, which triggered me immediately towards this comment, is the fact that you then have to pass the DaVinci (big-ish) options object to configure the FunTuple instance. It's coupling far too much and hence looks non-ideal.

Sorry, my 2 cents.