name 'MadGraph5Error' is not defined

[simone tentori]

I have written a model with NLO_CT and generated a UFO model. In this model I have both QCD couplings and NP couplings. When I try to run a process p p > t t~ [virt=NP] I have no problem.
When I try to run p p > t t~ [virt=all] or p p > t t~ [virt=QCD], after correctly generating output MY_OUT and pressing the command launch and confirming the parameter card, I obtain this error:

Command "launch" interrupted with error:
NameError : name 'MadGraph5Error' is not defined
Please report this bug on https://bugs.launchpad.net/mg5amcnlo
More information is found in 'MG5_debug'.
Please attach this file to your report.

Don't know what this error is.
Even more strange if I do not renormalize the fermion masses, there are no errors, any idea why this happens?
Many thanks to everyone who will respond. In the attachment I've put the MG5_debug

[Olivier Mattelaer (olivier-mattelaer)]

Ok, the error is quite cryptic... because the code crash in ... the handling of the error.

The real error message is "MadLoop could not initialize the process"

Which likely means that it fails to check helicity/zero loop for your process.
The mass of the particles are not running right?

Cheers,

Olivier

> On 3 Sep 2022, at 23:21, simone tentori <email address hidden> wrote:
>
> Public bug reported:
>
> I have written a model with NLO_CT and generated a UFO model. In this model I have both QCD couplings and NP couplings. When I try to run a process p p > t t~ [virt=NP] I have no problem.
> When I try to run p p > t t~ [virt=all] or p p > t t~ [virt=QCD], after correctly generating output MY_OUT and pressing the command launch and confirming the parameter card, I obtain this error:
>
> Command "launch" interrupted with error:
> NameError : name 'MadGraph5Error' is not defined
> Please report this bug on https://bugs.launchpad.net/mg5amcnlo
> More information is found in 'MG5_debug'.
> Please attach this file to your report.
>
> Don't know what this error is.
> Even more strange if I do not renormalize the fermion masses, there are no errors, any idea why this happens?
> Many thanks to everyone who will respond. In the attachment I've put the MG5_debug
>
> ** Affects: mg5amcnlo
> Importance: Undecided
> Status: New
>
> ** Attachment added: "mg5_debug"
> https://bugs.launchpad.net/bugs/1988652/+attachment/5613509/+files/MG5_debug
>
> --
> You received this bug notification because you are subscribed to
> MadGraph5_aMC@NLO.
> https://bugs.launchpad.net/bugs/1988652
>
> Title:
> name 'MadGraph5Error' is not defined
>
> Status in MadGraph5_aMC@NLO:
> New
>
> Bug description:
> I have written a model with NLO_CT and generated a UFO model. In this model I have both QCD couplings and NP couplings. When I try to run a process p p > t t~ [virt=NP] I have no problem.
> When I try to run p p > t t~ [virt=all] or p p > t t~ [virt=QCD], after correctly generating output MY_OUT and pressing the command launch and confirming the parameter card, I obtain this error:
>
> Command "launch" interrupted with error:
> NameError : name 'MadGraph5Error' is not defined
> Please report this bug on https://bugs.launchpad.net/mg5amcnlo
> More information is found in 'MG5_debug'.
> Please attach this file to your report.
>
> Don't know what this error is.
> Even more strange if I do not renormalize the fermion masses, there are no errors, any idea why this happens?
> Many thanks to everyone who will respond. In the attachment I've put the MG5_debug
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/mg5amcnlo/+bug/1988652/+subscriptions
>

[simone tentori (simone11)]

I have tried simpler processes to understand the problem together with
Davide Pagani. The problem seems related only to the d-quark. There's an
even more strange behaviour: if I launch the d d~ > t t~ [virt=QCD] without
touching the parameter card I obtain the error mentioned above, but if I
launch again the processes, changing only the d-mass order of magnitude
(not important bigger or smaller), Madgraph is now able to do the
computation. If I launch again returning the value of the d-mass to the
original one, Madgraph performs the computation without raising any error.
This only happens with the d-quark, even if in my model there's nothing
special about it. Please tell me if there are any attachments that could be useful.
Best Regards,
Simone

>

[Olivier Mattelaer (olivier-mattelaer)]

Sorry for the late answer on this.
Could you attach the model?

I guess that the issue is that the initialization of the loop fails for small mass due to some threshold. (like the code does not know if it is zero or not) Setting the mass to zero likely solves the issue or putting large. Changing the mass does not re-trigger the computation of non zero helicity/... so the code is likely going trough.

I have assign this to our loop expert who might have more precise insight.

CHeers,

Olivier

[simone tentori (simone11)]

Dear Olivier,
at that time I solved the problem putting all the masses to zero.
Unfortunately being the question from long ago I do not have a copy of the
old unworking model anymore

Simone

Il ven 20 gen 2023, 19:05 Olivier Mattelaer <email address hidden> ha
scritto:

> Sorry for the late answer on this.
> Could you attach the model?
>
> I guess that the issue is that the initialization of the loop fails for
> small mass due to some threshold. (like the code does not know if it is
> zero or not) Setting the mass to zero likely solves the issue or putting
> large. Changing the mass does not re-trigger the computation of non zero
> helicity/... so the code is likely going trough.
>
> I have assign this to our loop expert who might have more precise
> insight.
>
> CHeers,
>
> Olivier
>
> ** Changed in: mg5amcnlo
> Assignee: (unassigned) => Valentin Hirschi (valentin-hirschi)
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1988652
>
> Title:
> name 'MadGraph5Error' is not defined
>
> Status in MadGraph5_aMC@NLO:
> New
>
> Bug description:
> I have written a model with NLO_CT and generated a UFO model. In this
> model I have both QCD couplings and NP couplings. When I try to run a
> process p p > t t~ [virt=NP] I have no problem.
> When I try to run p p > t t~ [virt=all] or p p > t t~ [virt=QCD], after
> correctly generating output MY_OUT and pressing the command launch and
> confirming the parameter card, I obtain this error:
>
> Command "launch" interrupted with error:
> NameError : name 'MadGraph5Error' is not defined
> Please report this bug on https://bugs.launchpad.net/mg5amcnlo
> More information is found in 'MG5_debug'.
> Please attach this file to your report.
>
> Don't know what this error is.
> Even more strange if I do not renormalize the fermion masses, there are
> no errors, any idea why this happens?
> Many thanks to everyone who will respond. In the attachment I've put the
> MG5_debug
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/mg5amcnlo/+bug/1988652/+subscriptions
>
>

[Olivier Mattelaer (olivier-mattelaer)]

Sorry again for the long delay.
Setting the mass to zero is actually the correct thing to do.

Cheers,

Olivier

> On 20 Jan 2023, at 19:09, simone tentori <email address hidden> wrote:
>
> Dear Olivier,
> at that time I solved the problem putting all the masses to zero.
> Unfortunately being the question from long ago I do not have a copy of the
> old unworking model anymore
>
> Simone
>
> Il ven 20 gen 2023, 19:05 Olivier Mattelaer <<email address hidden> <mailto:<email address hidden>>> ha
> scritto:
>
>> Sorry for the late answer on this.
>> Could you attach the model?
>>
>> I guess that the issue is that the initialization of the loop fails for
>> small mass due to some threshold. (like the code does not know if it is
>> zero or not) Setting the mass to zero likely solves the issue or putting
>> large. Changing the mass does not re-trigger the computation of non zero
>> helicity/... so the code is likely going trough.
>>
>> I have assign this to our loop expert who might have more precise
>> insight.
>>
>> CHeers,
>>
>> Olivier
>>
>> ** Changed in: mg5amcnlo
>> Assignee: (unassigned) => Valentin Hirschi (valentin-hirschi)
>>
>> --
>> You received this bug notification because you are subscribed to the bug
>> report.
>> https://bugs.launchpad.net/bugs/1988652
>>
>> Title:
>> name 'MadGraph5Error' is not defined
>>
>> Status in MadGraph5_aMC@NLO:
>> New
>>
>> Bug description:
>> I have written a model with NLO_CT and generated a UFO model. In this
>> model I have both QCD couplings and NP couplings. When I try to run a
>> process p p > t t~ [virt=NP] I have no problem.
>> When I try to run p p > t t~ [virt=all] or p p > t t~ [virt=QCD], after
>> correctly generating output MY_OUT and pressing the command launch and
>> confirming the parameter card, I obtain this error:
>>
>> Command "launch" interrupted with error:
>> NameError : name 'MadGraph5Error' is not defined
>> Please report this bug on https://bugs.launchpad.net/mg5amcnlo
>> More information is found in 'MG5_debug'.
>> Please attach this file to your report.
>>
>> Don't know what this error is.
>> Even more strange if I do not renormalize the fermion masses, there are
>> no errors, any idea why this happens?
>> Many thanks to everyone who will respond. In the attachment I've put the
>> MG5_debug
>>
>> To manage notifications about this bug go to:
>> https://bugs.launchpad.net/mg5amcnlo/+bug/1988652/+subscriptions
>>
>>
>
> --
> You received this bug notification because you are subscribed to
> MadGraph5_aMC@NLO.
> https://bugs.launchpad.net/bugs/1988652
>
> Title:
> name 'MadGraph5Error' is not defined
>
> Status in MadGraph5_aMC@NLO:
> New
>
> Bug description:
> I have written a model with NLO_CT and generated a UFO model. In this model I have both QCD couplings and NP couplings. When I try to run a process p p > t t~ [virt=NP] I have no problem.
> When I try to run p p > t t~ [virt=all] or p p > t t~ [virt=QCD], after correctly generating output MY_OUT and pressing the command launch and confirming the parameter card, I obtain this error:
>
> Command "launch" interrupted with error:
> NameError : name 'MadGraph5Err...