> Hi,
>
> I have zero experience with FeynRules.
> So my only advise on that topic would be to contact FeynRules author (or
> to read the FR manual)
>
> Cheers,
>
> Olivier
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1803514
>
> Title:
> Bug running madgraph
>
> Status in MadGraph5_aMC@NLO:
> Incomplete
>
> Bug description:
> hi
>
> I was running the code generate g g > lg l g, lg > l j
> with all the model filed and particles properly defined but this is the
> error which iam
> getting.
>
> "Error when reading
> /home/arvind/HEP/Source/MG5_aMC_v2.6.4/MG5_aMC_v2_6_4/lep1/SubProcesses/P1_gg_xlg_x_lg/G1/results.dat
> Command "generate_events run_01" interrupted with error:
> ValueError : need more than 5 values to unpack."
>
> Thanks
> Arvind
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/mg5amcnlo/+bug/1803514/+subscriptions
>
Hey
Thanks, I'll look into it. A big thanks for bailing me out of this mess
Arvind
On Wed 28 Nov, 2018, 6:41 PM Olivier Mattelaer, <
<email address hidden>> wrote:
> Hi, /bugs.launchpad .net/bugs/ 1803514 HEP/Source/ MG5_aMC_ v2.6.4/ MG5_aMC_ v2_6_4/ lep1/SubProcess es/P1_gg_ xlg_x_lg/ G1/results. dat /bugs.launchpad .net/mg5amcnlo/ +bug/1803514/ +subscriptions
>
> I have zero experience with FeynRules.
> So my only advise on that topic would be to contact FeynRules author (or
> to read the FR manual)
>
> Cheers,
>
> Olivier
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https:/
>
> Title:
> Bug running madgraph
>
> Status in MadGraph5_aMC@NLO:
> Incomplete
>
> Bug description:
> hi
>
> I was running the code generate g g > lg l g, lg > l j
> with all the model filed and particles properly defined but this is the
> error which iam
> getting.
>
> "Error when reading
> /home/arvind/
> Command "generate_events run_01" interrupted with error:
> ValueError : need more than 5 values to unpack."
>
> Thanks
> Arvind
>
> To manage notifications about this bug go to:
> https:/
>