MadGraph5_aMC@NLO

NameError in v2.2.2 but not in v1.5.12

Bug #1395215 reported by Kunal Kumar
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
MadGraph5_aMC@NLO
Fix Released
Undecided
Unassigned

Bug Description

I get the following error when using a model created using Feynrules v2.0.17. in MG5_aMC v2.2.2
----------------
Command "compute_widths t w+ z h H H3p H3z H5pp H5p H5z H3p~ H5pp~ H5p~ --body_decay=2 --path=./param_card.dat" interrupted with error:
NameError : name 'mdl_MH' is not defined
----------------
I don't get this error in MG5 v1.5.12 and the param_card does get updated with decay widths,BRs.
Here's a section of MG5_debug (i've attached it as well)
---------------
Traceback (most recent call last):
  File "/Users/kunalkumar/Tools/MG5_aMC_v2_2_2/madgraph/interface/extended_cmd.py", line 879, in onecmd
    return self.onecmd_orig(line, **opt)
  File "/Users/kunalkumar/Tools/MG5_aMC_v2_2_2/madgraph/interface/extended_cmd.py", line 872, in onecmd_orig
    return func(arg, **opt)
  File "/Users/kunalkumar/Tools/MG5_aMC_v2_2_2/madgraph/interface/master_interface.py", line 318, in do_compute_widths
    return self.cmd.do_compute_widths(self, *args, **opts)
  File "/Users/kunalkumar/Tools/MG5_aMC_v2_2_2/madgraph/interface/madgraph_interface.py", line 6218, in do_compute_widths
    tmp_mass -= abs(eval("mdl_"+str(p.mass), data))
-------------

Thanks for your help!

Revision history for this message
Kunal Kumar (kunal-kunalkumar) wrote :
Revision history for this message
Olivier Mattelaer (olivier-mattelaer) wrote : Re: [Bug 1395215] [NEW] NameError in v2.2.2 but not in v1.5.12
Download full text (3.4 KiB)

Dear Kunal,

Thanks for this report. I have try to guess what the problem is, but I failed. I would really need your model in order to be able to reproduce your bug.
So could you attach it to this bug report? (or if you do not want to put it on public space, you can send it to me by email: <email address hidden>)

Cheers,

Olivier

On Nov 21, 2014, at 10:27 PM, Kunal Kumar <email address hidden> wrote:

> Public bug reported:
>
> I get the following error when using a model created using Feynrules v2.0.17. in MG5_aMC v2.2.2
> ----------------
> Command "compute_widths t w+ z h H H3p H3z H5pp H5p H5z H3p~ H5pp~ H5p~ --body_decay=2 --path=./param_card.dat" interrupted with error:
> NameError : name 'mdl_MH' is not defined
> ----------------
> I don't get this error in MG5 v1.5.12 and the param_card does get updated with decay widths,BRs.
> Here's a section of MG5_debug (i've attached it as well)
> ---------------
> Traceback (most recent call last):
> File "/Users/kunalkumar/Tools/MG5_aMC_v2_2_2/madgraph/interface/extended_cmd.py", line 879, in onecmd
> return self.onecmd_orig(line, **opt)
> File "/Users/kunalkumar/Tools/MG5_aMC_v2_2_2/madgraph/interface/extended_cmd.py", line 872, in onecmd_orig
> return func(arg, **opt)
> File "/Users/kunalkumar/Tools/MG5_aMC_v2_2_2/madgraph/interface/master_interface.py", line 318, in do_compute_widths
> return self.cmd.do_compute_widths(self, *args, **opts)
> File "/Users/kunalkumar/Tools/MG5_aMC_v2_2_2/madgraph/interface/madgraph_interface.py", line 6218, in do_compute_widths
> tmp_mass -= abs(eval("mdl_"+str(p.mass), data))
> -------------
>
> Thanks for your help!
>
> ** Affects: mg5amcnlo
> Importance: Undecided
> Status: New
>
> ** Attachment added: "MG5_debug"
> https://bugs.launchpad.net/bugs/1395215/+attachment/4265385/+files/MG5_debug
>
> --
> You received this bug notification because you are subscribed to
> MadGraph5_aMC@NLO.
> https://bugs.launchpad.net/bugs/1395215
>
> Title:
> NameError in v2.2.2 but not in v1.5.12
>
> Status in MadGraph5_aMC@NLO Generator:
> New
>
> Bug description:
> I get the following error when using a model created using Feynrules v2.0.17. in MG5_aMC v2.2.2
> ----------------
> Command "compute_widths t w+ z h H H3p H3z H5pp H5p H5z H3p~ H5pp~ H5p~ --body_decay=2 --path=./param_card.dat" interrupted with error:
> NameError : name 'mdl_MH' is not defined
> ----------------
> I don't get this error in MG5 v1.5.12 and the param_card does get updated with decay widths,BRs.
> Here's a section of MG5_debug (i've attached it as well)
> ---------------
> Traceback (most recent call last):
> File "/Users/kunalkumar/Tools/MG5_aMC_v2_2_2/madgraph/interface/extended_cmd.py", line 879, in onecmd
> return self.onecmd_orig(line, **opt)
> File "/Users/kunalkumar/Tools/MG5_aMC_v2_2_2/madgraph/interface/extended_cmd.py", line 872, in onecmd_orig
> return func(arg, **opt)
> File "/Users/kunalkumar/Tools/MG5_aMC_v2_2_2/madgraph/interface/master_interface.py", line 318, in do_compute_widths
> return self.cmd.do_compute_widths(self, *args, **opts)
> File "/Users/kunalkumar/Tools/MG5_aMC_v2_2_2/madgrap...

Read more...

Revision history for this message
Kunal Kumar (kunal-kunalkumar) wrote :

I've attached the MG5 model folder. It's an implementation of
the Georgi-Machacek model which is the SM extended by a real and
a complex SU(2) triplet of scalars .

 The "NameError : name 'mdl_MH' is not defined" makes me think it might
be related to the fact that in this model I use MH for the other higgs
(the 125 GeV resonance mass is labelled Mh), but I'm not sure since there
were no issues with this model in MG5 v1.5.12.

Thanks for your help!

Revision history for this message
Olivier Mattelaer (olivier-mattelaer) wrote : Re: [Bug 1395215] NameError in v2.2.2 but not in v1.5.12

Hi,

> The "NameError : name 'mdl_MH' is not defined" makes me think it might
> be related to the fact that in this model I use MH for the other higgs
> (the 125 GeV resonance mass is labelled Mh), but I'm not sure since there
> were no issues with this model in MG5 v1.5.12.

This is clearly the problem. Now I need to find a way to fix such problem.
The reason for this is that we do not like to have different parameter different by only the case.
So we rename one of the two to mh__2. But looks like we didn’t apply the expression change to the formula read from
decays.py file.

I’ll investigate more and put here a patch as soon as i have one.

Thanks,

Olivier

On Nov 22, 2014, at 4:47 AM, Kunal Kumar <email address hidden> wrote:

> I've attached the MG5 model folder. It's an implementation of
> the Georgi-Machacek model which is the SM extended by a real and
> a complex SU(2) triplet of scalars .
>
> The "NameError : name 'mdl_MH' is not defined" makes me think it might
> be related to the fact that in this model I use MH for the other higgs
> (the 125 GeV resonance mass is labelled Mh), but I'm not sure since there
> were no issues with this model in MG5 v1.5.12.
>
> Thanks for your help!
>
> ** Attachment added: "GM_new_Nov21_UFO.tar.gz"
> https://bugs.launchpad.net/mg5amcnlo/+bug/1395215/+attachment/4265508/+files/GM_new_Nov21_UFO.tar.gz
>
> --
> You received this bug notification because you are subscribed to
> MadGraph5_aMC@NLO.
> https://bugs.launchpad.net/bugs/1395215
>
> Title:
> NameError in v2.2.2 but not in v1.5.12
>
> Status in MadGraph5_aMC@NLO Generator:
> New
>
> Bug description:
> I get the following error when using a model created using Feynrules v2.0.17. in MG5_aMC v2.2.2
> ----------------
> Command "compute_widths t w+ z h H H3p H3z H5pp H5p H5z H3p~ H5pp~ H5p~ --body_decay=2 --path=./param_card.dat" interrupted with error:
> NameError : name 'mdl_MH' is not defined
> ----------------
> I don't get this error in MG5 v1.5.12 and the param_card does get updated with decay widths,BRs.
> Here's a section of MG5_debug (i've attached it as well)
> ---------------
> Traceback (most recent call last):
> File "/Users/kunalkumar/Tools/MG5_aMC_v2_2_2/madgraph/interface/extended_cmd.py", line 879, in onecmd
> return self.onecmd_orig(line, **opt)
> File "/Users/kunalkumar/Tools/MG5_aMC_v2_2_2/madgraph/interface/extended_cmd.py", line 872, in onecmd_orig
> return func(arg, **opt)
> File "/Users/kunalkumar/Tools/MG5_aMC_v2_2_2/madgraph/interface/master_interface.py", line 318, in do_compute_widths
> return self.cmd.do_compute_widths(self, *args, **opts)
> File "/Users/kunalkumar/Tools/MG5_aMC_v2_2_2/madgraph/interface/madgraph_interface.py", line 6218, in do_compute_widths
> tmp_mass -= abs(eval("mdl_"+str(p.mass), data))
> -------------
>
> Thanks for your help!
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/mg5amcnlo/+bug/1395215/+subscriptions

Revision history for this message
Olivier Mattelaer (olivier-mattelaer) wrote :

Hi,

Now I can really confirm that the bug was linked to that, but this was different that what explained before.
Here is this patch to make it work:

=== modified file 'madgraph/interface/madgraph_interface.py'
--- old/madgraph/interface/madgraph_interface.py 2014-11-05 17:34:19 +0000
+++ new/madgraph/interface/madgraph_interface.py 2014-11-22 14:27:00 +0000
@@ -6213,9 +6213,12 @@
                     tmp_mass = mass
                     for p in mode:
                         try:
- tmp_mass -= abs(eval(str(p.mass), data))
+ value_mass = eval(str(p.mass), data)
                         except Exception:
- tmp_mass -= abs(eval("mdl_"+str(p.mass), data))
+ # the p object can still be UFO reference. since the
+ # mass name might hve change load back the MG5 one.
+ value_mass = eval(str(model.get_particle(p.pdg_code).get('mass')), data)
+ tmp_mass -= abs(value_mass)
                     if tmp_mass <=0:
                         continue

Cheers,

Olivier

Changed in mg5amcnlo:
status: New → Fix Released
Revision history for this message
Kunal Kumar (kunal-kunalkumar) wrote :

Hi Olivier,

Thanks! That patch does solve the problem.

Thanks!
Kunal

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.