:) I created this issue, indeed. But we will implement MVA when someone needs it. IF RTA needs it, you should define the schedule as it's more critical for you. We can add functors to be used offline any time.
Hi all, are there any news on this? From DPA we want to finalise on Phys#19 (closed) this year and will be discussing the how-to at our coords meeting tomorrow.
In !2588 (merged) I ported the code from TMVATransform so that TMVA can now be invoked from the MVA functor. The code is essentially the same just with a few less unnecessary checks and of course adapted to live under MVA. I was able to test that the inputs were being fed correctly into a BDT and that the output was ok too.
The MR was reverted to draft just in case some other test was necessary and maybe we could add some debug/verbose behaviour. Otherwise it is ready to merge
Morning @aalfonso. Thank you for your quick reply. This sounds great and it would be good to see this merged and in use asap, for obvious reasons. But that means "replacement work" for RTA to ideally get rid of the dependency on MVADictTools (we are likely to have some work also on the offline side). @mvesteri, @poluekt, can this be given consideration and a push? First things first, let's get !2588 (merged) in .
(Sorry for the "push" but better to raise the hand now for the benefit of us all than the day before a beam test or alike, right? But acknowledged that priorities exist ... and are functions of time.)