Functionality to create multiple decay descriptors from a dict when particles have multiple decay modes about decaylanguage HOT 4 CLOSED

Thanks for the comment/feedback, Adam. Let me post here what I exchanged in chat with you, as a starting point:

The dict representations can store "anything" (dec files are wild) but a DecayChain is in the present incantation a simple thing, only for a decay chain, not for n possible decay chains. If I understand quickly you rather want some splitting function that spits out a set/list of DecayChain instances?

This is very fair and something that has been on the list in my head since a while ... Actually for the same reason as you, meaning when I think in terms of searches of final states for some use-case ...

Let's try and get something worked out.

from decaylanguage.

Yes, that's what I'd like. I was thinking of the word "flattening" but this is used already in another context, so how about "expanding" the decay dicts to a list of unique decay chains.

Chris and I have written some similar logic already for the NTuple Wizard decays.py#L509-579 where it traverses down to the bottom of the tree (the final state) and works its way back up, collecting all combinations that arise from multiple decay modes (and PID substitutions, although that's not relevant here).

from decaylanguage.

I mean, they don't have to be DecayChain objects since I'm unsure if it can handle e.g. $B_s \to (\phi \to K^+ K^-) (\phi \to \pi^+ \pi^- \pi^0)$ without giving each $\phi$ a unique name. I'd be happy with just strings (decay descriptors) as the output.

from decaylanguage.

Yes "expanding" sounds good to me, and it is easiest in a first implementation to only provide the output as a string (or a DaughtersDict on which you call to_string, if you prefer) .

Indeed there are some limitations and right now your decay Bs -> phi phi with 2 different phi decays would need to have the phi's aliased to different names. This is not too crazy if one things that the decays are different, but it is for sure a limitation in certain contexts.

Let's sort in the immediate future your use-case. I guess you will need a release as soon as this is done. Just let me know.

Thanks again,

from decaylanguage.