El vie., 21 dic. 2018 a las 21:40, Olivier Mattelaer (<
<email address hidden>>) escribió:
> In this case, I would do the following
> 1) running everything at fix scale
> 2) generate three sample
> - the one with the decay chain
> - the opposite one (the $ syntax)
> - the full one
> 3) compare the difference between the sum of the two first and the third.
>
> This comparison is typically done in most of my tutorials.
>
> https://cp3.irmp.ucl.ac.be/projects/madgraph/attachment/wiki/MCNET2017/17_06_02_tuto_mcnet.pdf
>
> Cheers,
>
> Olivier
>
> ** Changed in: mg5amcnlo
> Status: New => Invalid
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1805107
>
> Title:
> Madspin fails to decay events for large couplings
>
> Status in MadGraph5_aMC@NLO:
> Invalid
>
> Bug description:
> Hi Olivier,
>
> I am running a LO event generation with decays through Madspin. I
> implemented my model in Feynrules, and I basically have SM + new
> scalar doublet with slepton quantum numbers + new fermion singlet
> under SM. You helped me with a tricky bug in "#1801760 Madspin fails
> with majorana particle" a couple of weeks ago, so you might remember
> the model.
>
> I found another issue. When Madspin decays the events, I am getting
> the following warning for some of them:
>
> INFO: All production process does not have the same total Branching
> Ratio.
> Therefore the total number of events after decay
> will be lower than the original file.
> [max_br = 0.99515608014, min_br = 0.992471423458]
>
> which is not too bad, but if the coupling for the relevant vertex
> (phil-psi-lepton) is too large (~3), Madspin gets stuck decaying the
> events:
>
> ...
> ...
> INFO: Event 291/300 : 2.8s
> INFO: Event 296/300 : 2.8s
> INFO: All production process does not have the same total Branching
> Ratio.
> Therefore the total number of events after decay
> will be lower than the original file.
> [max_br = 0.99515608014, min_br = 0.992471423458]
> INFO:
> INFO: Decaying the events...
>
>
> Any clues about this one? Thanks!
>
> Cheers,
>
> Pablo
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/mg5amcnlo/+bug/1805107/+subscriptions
>
Thanks Olivier, that solved my question!
Cheers,
Pablo
El vie., 21 dic. 2018 a las 21:40, Olivier Mattelaer (<
<email address hidden>>) escribió:
> In this case, I would do the following /cp3.irmp. ucl.ac. be/projects/ madgraph/ attachment/ wiki/MCNET2017/ 17_06_02_ tuto_mcnet. pdf /bugs.launchpad .net/bugs/ 1805107 /bugs.launchpad .net/mg5amcnlo/ +bug/1805107/ +subscriptions
> 1) running everything at fix scale
> 2) generate three sample
> - the one with the decay chain
> - the opposite one (the $ syntax)
> - the full one
> 3) compare the difference between the sum of the two first and the third.
>
> This comparison is typically done in most of my tutorials.
>
> https:/
>
> Cheers,
>
> Olivier
>
> ** Changed in: mg5amcnlo
> Status: New => Invalid
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https:/
>
> Title:
> Madspin fails to decay events for large couplings
>
> Status in MadGraph5_aMC@NLO:
> Invalid
>
> Bug description:
> Hi Olivier,
>
> I am running a LO event generation with decays through Madspin. I
> implemented my model in Feynrules, and I basically have SM + new
> scalar doublet with slepton quantum numbers + new fermion singlet
> under SM. You helped me with a tricky bug in "#1801760 Madspin fails
> with majorana particle" a couple of weeks ago, so you might remember
> the model.
>
> I found another issue. When Madspin decays the events, I am getting
> the following warning for some of them:
>
> INFO: All production process does not have the same total Branching
> Ratio.
> Therefore the total number of events after decay
> will be lower than the original file.
> [max_br = 0.99515608014, min_br = 0.992471423458]
>
> which is not too bad, but if the coupling for the relevant vertex
> (phil-psi-lepton) is too large (~3), Madspin gets stuck decaying the
> events:
>
> ...
> ...
> INFO: Event 291/300 : 2.8s
> INFO: Event 296/300 : 2.8s
> INFO: All production process does not have the same total Branching
> Ratio.
> Therefore the total number of events after decay
> will be lower than the original file.
> [max_br = 0.99515608014, min_br = 0.992471423458]
> INFO:
> INFO: Decaying the events...
>
>
> Any clues about this one? Thanks!
>
> Cheers,
>
> Pablo
>
> To manage notifications about this bug go to:
> https:/
>