Comment 2 for bug 1737150

Cool thanks! I will try it out.

Cheers,

Benj

> On 11 Jan 2018, at 16:18 , Olivier Mattelaer <email address hidden> wrote:
>
> Problem fixed in 2.6.2.
> It was a due to a check for loop-induced that was not handling decay-chain.
>
> Cheers,
>
> Olivier
>
> ** Changed in: mg5amcnlo
> Status: New => Fix Committed
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1737150
>
> Title:
> Madspin/ 1>N bug when one decay use decay chain but not the other
>
> Status in MadGraph5_aMC@NLO:
> Fix Committed
>
> Bug description:
> The following script crash:
>
> generate w+ > e+ ve
> add process t > w+ b, w+ > l+ vl
> output
>
> with error:
>
> Command "import /Users/omatt/mgdev/2.6.1/cmd2" interrupted in sub-command:
> "output" with error:
> PhysicsObjectError : process is not a valid property for this object: DecayChainAmplitude
>
> Valid property are ['amplitudes', 'decay_chains']
> Please report this bug on https://bugs.launchpad.net/mg5amcnlo
> More information is found in 'MG5_debug'.
> Please attach this file to your report.
>
> This seems related to the mix between decay-chain and standard decay.
> This also impacts MadSpin (for obvious reason)
>
> (reported via email by Benj --for a BSM model--
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/mg5amcnlo/+bug/1737150/+subscriptions