Functor to replace MCTupleToolPrompt

Functor writing campaign: https://gitlab.cern.ch/lhcb-dpa/project/-/issues/61

Functor to replace the Run 2 tuple tool here.

General idea:

• loop over ancestral history of a MCParticle
• get the true (PDG) lifetimes of each ancestor
• if any lifetime > 0.1 fs the MCParticle is considered not prompt

If not prompt, the Run 2 tool also created _ID and _KEY branches of the first long lived ancestor.
Changed here to first create FirstLongLivedAncestor Functor with IsPrompt Functor built on top. (thanks to @jzhuo)

This should be tested with: DaVinci!800 (merged) and Analysis!937 (merged)

added Functors label

assigned to @aburke

added RTA label

Thanks @aburke for creating this tool! Just a little bit of comment, since MCTupleToolPrompt do more than just check if a particle is prompt (it also returns the first long-lived MCP ancestor's ID and key), would be nice to have a functor which returns the first long-lived MCP ancestor and then create this isPrompt functor on top, something like if not fist long-lived MCP ancestor is found them return true to isPrompt. WDYT?

Hi, you mean to call isPrompt recursively on each ancestor until isPrompt returns true?

Hi @jzhuo , at the moment I don't have time to implement the extra functor discussed above. We need an IsPrompt Functor for charm early measurements, preferably in the next release so that we have the branch in our upcoming MC production. Can we merge what I have in place and update it to include the F.FirstLongLivedDecayOrigin functor soon?

added 32 commits

• 07ca3655...b84746ff - 27 commits from branch master
• 84dcb062 - Merge branch 'master' into aburke/mcprompt
• d3437725 - Adding new value functor
• a054eb8b - Change from IsPrompt to FirstLongLivedAncestor
• 09380183 - Define functors
• 20a3f16f - Add tests

Compare with previous version

assigned to @jzhuo

added DPA-WP3 MC checking labels

added 1 commit

• c6f0e750 - Fixed formatting

Compare with previous version

resolved all threads

added 1 commit

• f0c89c42 - Updating docs

Compare with previous version

requested review from @amathad, @pkoppenb, and @erodrigu

removed review request for @erodrigu

[Removing myself as I'm not responsible for Rec as project and am not a FunctorCore expert/responsible.]