--modelname with madspin

Bug #1596226 reported by Olivier Mattelaer
12
This bug affects 2 people
Affects Status Importance Assigned to Milestone
MadGraph5_aMC@NLO
Fix Released
Undecided
Unassigned

Bug Description

Hi

I'm trying to calculate cross section of a process with a decay chain by using madspin. However it gives me the following error:

Error detected in "generate_events run_02"
write debug file /home/jack/packages/MG5_aMC_v2_4_0/chachabar/run_02_tag_2_debug.log
If you need help with this issue please contact us on https://answers.launchpad.net/mg5amcnlo
MadGraph5Error : h3 particles with pdg code 45 is in conflict with MG convention name for particle 36.
Use -modelname in order to use the particles name defined in the model and not the MadGraph5_aMC@NLO convention

The problem is I'm already importing the model by using 'import model $model --modelname' which generated by SARAH and masses and decay tables were calculated by SPheno with proper flags for madgraph. I also tried to run it directly from madspin itself instead of launching it from mg5, however it gave me the same error all the time. Is there any way to fix this?

Thanks

Best regards
Jack

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

Hi Jack,

Can you attach your model and the debug file automatically generated?
I have tried to reproduce your bug with another model but it went trough without any problem.
So the best would be to test what's happening with your model.

Cheers,

Olivier

Revision history for this message
Jack Y. Araz (jackaraz) wrote :
Download full text (4.7 KiB)

Hi Oliver

model file is attached and I'm also including debug file below. Thanks a lot

jack

run_01_tag_2_debug.log:

generate_events run_01
Traceback (most recent call last):
  File "/home/jack/packages/MG5_aMC_v2_4_0/madgraph/interface/extended_cmd.py", line 1009, in onecmd
    return self.onecmd_orig(line, **opt)
  File "/home/jack/packages/MG5_aMC_v2_4_0/madgraph/interface/extended_cmd.py", line 964, in onecmd_orig
    return func(arg, **opt)
  File "/home/jack/packages/MG5_aMC_v2_4_0/madgraph/interface/madevent_interface.py", line 2017, in do_generate_events
    self.exec_cmd('decay_events -from_cards', postcmd=False)
  File "/home/jack/packages/MG5_aMC_v2_4_0/madgraph/interface/extended_cmd.py", line 1035, in exec_cmd
    stop = Cmd.onecmd_orig(current_interface, line, **opt)
  File "/home/jack/packages/MG5_aMC_v2_4_0/madgraph/interface/extended_cmd.py", line 964, in onecmd_orig
    return func(arg, **opt)
  File "/home/jack/packages/MG5_aMC_v2_4_0/madgraph/interface/common_run_interface.py", line 2000, in do_decay_events
    madspin_cmd = interface_madspin.MadSpinInterface(args[0])
  File "/home/jack/packages/MG5_aMC_v2_4_0/madgraph/various/misc.py", line 169, in f_with_no_logger
    out = f(self, *args, **opt)
  File "/home/jack/packages/MG5_aMC_v2_4_0/MadSpin/interface_madspin.py", line 103, in __init__
    self.do_import(event_path)
  File "/home/jack/packages/MG5_aMC_v2_4_0/MadSpin/interface_madspin.py", line 236, in do_import
    self.mg5cmd.exec_cmd(line, printcmd=False, precmd=False, postcmd=False)
  File "/home/jack/packages/MG5_aMC_v2_4_0/madgraph/interface/extended_cmd.py", line 1035, in exec_cmd
    stop = Cmd.onecmd_orig(current_interface, line, **opt)
  File "/home/jack/packages/MG5_aMC_v2_4_0/madgraph/interface/extended_cmd.py", line 964, in onecmd_orig
    return func(arg, **opt)
  File "/home/jack/packages/MG5_aMC_v2_4_0/madgraph/interface/master_interface.py", line 497, in do_set
    return self.cmd.do_set(self, *args, **opts)
  File "/home/jack/packages/MG5_aMC_v2_4_0/madgraph/interface/madgraph_interface.py", line 6790, in do_set
    MadGraphCmd.do_import(self,'model %s' %model_name, force=True)
  File "/home/jack/packages/MG5_aMC_v2_4_0/madgraph/interface/madgraph_interface.py", line 4943, in do_import
    self._curr_model.pass_particles_name_in_mg_default()
  File "/home/jack/packages/MG5_aMC_v2_4_0/madgraph/core/base_objects.py", line 1457, in pass_particles_name_in_mg_default
    check_name_free(self, default[pdg])
  File "/home/jack/packages/MG5_aMC_v2_4_0/madgraph/core/base_objects.py", line 1446, in check_name_free
    (part.get_name(), part.get_pdg_code(), pdg)
MadGraph5Error: h3 particles with pdg code 45 is in conflict with MG convention name for particle 36.
 Use -modelname in order to use the particles name defined in the model and not the MadGraph5_aMC@NLO convention
                              Run Options
                              -----------
               stdout_level : 20 (user set)

                         MadEvent Options
                         ----------------
     automatic_html_opening : False (user set)
        notification_center : True
          cluster_temp_pa...

Read more...

Revision history for this message
Olivier Mattelaer (olivier-mattelaer) wrote : Re: [Bug 1596226] --modelname with madspin
Download full text (7.0 KiB)

Thanks to you to report this bug, this allow us to fix it.

Here is the patch:

=== modified file 'madgraph/interface/madgraph_interface.py'
--- madgraph/interface/madgraph_interface.py 2016-06-20 20:28:32 +0000
+++ madgraph/interface/madgraph_interface.py 2016-06-26 09:23:16 +0000
@@ -6762,6 +6762,11 @@
                     able_to_mod = False
                     if log: logger.warning('Note that Feynman gauge is not allowed for your current model %s' \
                                            % self._curr_model.get('name'))
+
+ if self.options['gauge'] == args[1]:
+ return
+
+
             self.options[args[0]] = args[1]

Thanks,

Olivier

> On Jun 26, 2016, at 00:34, jackaraz <email address hidden> wrote:
>
> Hi Oliver
>
> model file is attached and I'm also including debug file below. Thanks a
> lot
>
> jack
>
>
> run_01_tag_2_debug.log:
>
> generate_events run_01
> Traceback (most recent call last):
> File "/home/jack/packages/MG5_aMC_v2_4_0/madgraph/interface/extended_cmd.py", line 1009, in onecmd
> return self.onecmd_orig(line, **opt)
> File "/home/jack/packages/MG5_aMC_v2_4_0/madgraph/interface/extended_cmd.py", line 964, in onecmd_orig
> return func(arg, **opt)
> File "/home/jack/packages/MG5_aMC_v2_4_0/madgraph/interface/madevent_interface.py", line 2017, in do_generate_events
> self.exec_cmd('decay_events -from_cards', postcmd=False)
> File "/home/jack/packages/MG5_aMC_v2_4_0/madgraph/interface/extended_cmd.py", line 1035, in exec_cmd
> stop = Cmd.onecmd_orig(current_interface, line, **opt)
> File "/home/jack/packages/MG5_aMC_v2_4_0/madgraph/interface/extended_cmd.py", line 964, in onecmd_orig
> return func(arg, **opt)
> File "/home/jack/packages/MG5_aMC_v2_4_0/madgraph/interface/common_run_interface.py", line 2000, in do_decay_events
> madspin_cmd = interface_madspin.MadSpinInterface(args[0])
> File "/home/jack/packages/MG5_aMC_v2_4_0/madgraph/various/misc.py", line 169, in f_with_no_logger
> out = f(self, *args, **opt)
> File "/home/jack/packages/MG5_aMC_v2_4_0/MadSpin/interface_madspin.py", line 103, in __init__
> self.do_import(event_path)
> File "/home/jack/packages/MG5_aMC_v2_4_0/MadSpin/interface_madspin.py", line 236, in do_import
> self.mg5cmd.exec_cmd(line, printcmd=False, precmd=False, postcmd=False)
> File "/home/jack/packages/MG5_aMC_v2_4_0/madgraph/interface/extended_cmd.py", line 1035, in exec_cmd
> stop = Cmd.onecmd_orig(current_interface, line, **opt)
> File "/home/jack/packages/MG5_aMC_v2_4_0/madgraph/interface/extended_cmd.py", line 964, in onecmd_orig
> return func(arg, **opt)
> File "/home/jack/packages/MG5_aMC_v2_4_0/madgraph/interface/master_interface.py", line 497, in do_set
> return self.cmd.do_set(self, *args, **opts)
> File "/home/jack/packages/MG5_aMC_v2_4_0/madgraph/interface/madgraph_interface.py", line 6790, in do_set
> MadGraphCmd.do_import(self,'model %s' %model_name, force=True)
> File "/home/jack/packages/MG5_aMC_v2_4_0/madgraph/interface/madgraph_interface.py", line 4943, in do_import
> self._curr_model.pass_particles_name_in_mg_default()
> File "/home/jack/packages/MG5_aMC_v2_4_0/madgraph/core/base_objects...

Read more...

Revision history for this message
Jack Y. Araz (jackaraz) wrote :

Thanks Oliver, however I'm getting same error again after changing the lines that you wrote above. I also tried to do it from madspin directly but its still giving the same error here is the debug file that I got from madspin, hope it helps:

MS_debug:

Traceback (most recent call last):
  File "/home/jack/packages/MG5_aMC_v2_4_0/madgraph/interface/extended_cmd.py", line 1009, in onecmd
    return self.onecmd_orig(line, **opt)
  File "/home/jack/packages/MG5_aMC_v2_4_0/madgraph/interface/extended_cmd.py", line 964, in onecmd_orig
    return func(arg, **opt)
  File "/home/jack/packages/MG5_aMC_v2_4_0/MadSpin/interface_madspin.py", line 200, in do_import
    self.mg5cmd.exec_cmd(line, printcmd=False, precmd=False, postcmd=False)
  File "/home/jack/packages/MG5_aMC_v2_4_0/madgraph/interface/extended_cmd.py", line 1035, in exec_cmd
    stop = Cmd.onecmd_orig(current_interface, line, **opt)
  File "/home/jack/packages/MG5_aMC_v2_4_0/madgraph/interface/extended_cmd.py", line 964, in onecmd_orig
    return func(arg, **opt)
  File "/home/jack/packages/MG5_aMC_v2_4_0/madgraph/interface/master_interface.py", line 497, in do_set
    return self.cmd.do_set(self, *args, **opts)
  File "/home/jack/packages/MG5_aMC_v2_4_0/madgraph/interface/madgraph_interface.py", line 6794, in do_set
    MadGraphCmd.do_import(self,'model %s' %model_name, force=True)
  File "/home/jack/packages/MG5_aMC_v2_4_0/madgraph/interface/madgraph_interface.py", line 4943, in do_import
    self._curr_model.pass_particles_name_in_mg_default()
  File "/home/jack/packages/MG5_aMC_v2_4_0/madgraph/core/base_objects.py", line 1457, in pass_particles_name_in_mg_default
    check_name_free(self, default[pdg])
  File "/home/jack/packages/MG5_aMC_v2_4_0/madgraph/core/base_objects.py", line 1446, in check_name_free
    (part.get_name(), part.get_pdg_code(), pdg)
MadGraph5Error: h3 particles with pdg code 45 is in conflict with MG convention name for particle 36.
 Use -modelname in order to use the particles name defined in the model and not the MadGraph5_aMC@NLO convention
Value of current Options:
                 spinmode : madspin
             onlyhelicity : False
      max_weight_ps_point : 400
                 nb_sigma : 4.51217354724
                 run_card : None
   Nevents_for_max_weigth : 75
                   BW_cut : 15.0
              use_old_dir : False
               max_weight : -1
                 curr_dir : /home/jack/packages/MG5_aMC_v2_4_0/chachabar/Events/run_01/../..
                   ms_dir : None
      max_running_process : 100

Revision history for this message
Olivier Mattelaer (olivier-mattelaer) wrote :
Download full text (4.5 KiB)

Hi,

That modification works nicely on my laptop.
Are you sure that you have implemented it?
If so could you add the following print statement before the line that you have modify:
print self.options[‘gauge’], args[1]
(put the correct number of space to match the indentation as required by python.

In my case those two appears to be identical which then quit the function leading to the crash (since they are actually nothing to do).

Cheers,

Olivier

> On Jun 26, 2016, at 16:35, jackaraz <email address hidden> wrote:
>
> Thanks Oliver, however I'm getting same error again after changing the
> lines that you wrote above. I also tried to do it from madspin directly
> but its still giving the same error here is the debug file that I got
> from madspin, hope it helps:
>
> MS_debug:
>
> Traceback (most recent call last):
> File "/home/jack/packages/MG5_aMC_v2_4_0/madgraph/interface/extended_cmd.py", line 1009, in onecmd
> return self.onecmd_orig(line, **opt)
> File "/home/jack/packages/MG5_aMC_v2_4_0/madgraph/interface/extended_cmd.py", line 964, in onecmd_orig
> return func(arg, **opt)
> File "/home/jack/packages/MG5_aMC_v2_4_0/MadSpin/interface_madspin.py", line 200, in do_import
> self.mg5cmd.exec_cmd(line, printcmd=False, precmd=False, postcmd=False)
> File "/home/jack/packages/MG5_aMC_v2_4_0/madgraph/interface/extended_cmd.py", line 1035, in exec_cmd
> stop = Cmd.onecmd_orig(current_interface, line, **opt)
> File "/home/jack/packages/MG5_aMC_v2_4_0/madgraph/interface/extended_cmd.py", line 964, in onecmd_orig
> return func(arg, **opt)
> File "/home/jack/packages/MG5_aMC_v2_4_0/madgraph/interface/master_interface.py", line 497, in do_set
> return self.cmd.do_set(self, *args, **opts)
> File "/home/jack/packages/MG5_aMC_v2_4_0/madgraph/interface/madgraph_interface.py", line 6794, in do_set
> MadGraphCmd.do_import(self,'model %s' %model_name, force=True)
> File "/home/jack/packages/MG5_aMC_v2_4_0/madgraph/interface/madgraph_interface.py", line 4943, in do_import
> self._curr_model.pass_particles_name_in_mg_default()
> File "/home/jack/packages/MG5_aMC_v2_4_0/madgraph/core/base_objects.py", line 1457, in pass_particles_name_in_mg_default
> check_name_free(self, default[pdg])
> File "/home/jack/packages/MG5_aMC_v2_4_0/madgraph/core/base_objects.py", line 1446, in check_name_free
> (part.get_name(), part.get_pdg_code(), pdg)
> MadGraph5Error: h3 particles with pdg code 45 is in conflict with MG convention name for particle 36.
> Use -modelname in order to use the particles name defined in the model and not the MadGraph5_aMC@NLO convention
> Value of current Options:
> spinmode : madspin
> onlyhelicity : False
> max_weight_ps_point : 400
> nb_sigma : 4.51217354724
> run_card : None
> Nevents_for_max_weigth : 75
> BW_cut : 15.0
> use_old_dir : False
> max_weight : -1
> curr_dir : /home/jack/packages/MG5_aMC_v2_4_0/chachabar/Events/run_01/../..
> ms_dir : None
> max_running_process : 100
>
...

Read more...

Revision history for this message
Jack Y. Araz (jackaraz) wrote :

Hi Oliver

Sorry for the trouble but I still couldn't figured it out, I'm getting exactly the same error, thought it might be due to the indentation and changed it couple times but still the same error. Also with print I'm just getting the following:

Traceback (most recent call last):
  File "./bin/mg5_aMC", line 120, in <module>
    import madgraph.interface.master_interface as interface
  File "/home/jack/packages/MG5_aMC_v2_4_0/madgraph/interface/master_interface.py", line 43, in <module>
    import madgraph.interface.madgraph_interface as MGcmd
  File "/home/jack/packages/MG5_aMC_v2_4_0/madgraph/interface/madgraph_interface.py", line 6766
SyntaxError: Non-ASCII character '\xe2' in file /home/jack/packages/MG5_aMC_v2_4_0/madgraph/interface/madgraph_interface.py on line 6766, but no encoding declared; see http://www.python.org/peps/pep-0263.html for details

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

Hi,

> SyntaxError: Non-ASCII character ‘\xe2' in file /home/jack/packages/MG5_aMC_v2_4_0/madgraph/interface/madgraph_interface.py on line 6766, but no encoding declared; see http://www.python.org/peps/pep-0263.html for details

This is a formatting problem due to some weird formatting added by the mail client (probably mine).
This is typically the single or double quote which are automatically replaced by something more fancy.
The problem are those around the gauge term.

Cheers,

Olivier

> On Jun 27, 2016, at 03:28, jackaraz <email address hidden> wrote:
>
> Hi Oliver
>
> Sorry for the trouble but I still couldn't figured it out, I'm getting
> exactly the same error, thought it might be due to the indentation and
> changed it couple times but still the same error. Also with print I'm
> just getting the following:
>
> Traceback (most recent call last):
> File "./bin/mg5_aMC", line 120, in <module>
> import madgraph.interface.master_interface as interface
> File "/home/jack/packages/MG5_aMC_v2_4_0/madgraph/interface/master_interface.py", line 43, in <module>
> import madgraph.interface.madgraph_interface as MGcmd
> File "/home/jack/packages/MG5_aMC_v2_4_0/madgraph/interface/madgraph_interface.py", line 6766
> SyntaxError: Non-ASCII character '\xe2' in file /home/jack/packages/MG5_aMC_v2_4_0/madgraph/interface/madgraph_interface.py on line 6766, but no encoding declared; see http://www.python.org/peps/pep-0263.html for details
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1596226
>
> Title:
> --modelname with madspin
>
> Status in MadGraph5_aMC@NLO:
> New
>
> Bug description:
> Hi
>
> I'm trying to calculate cross section of a process with a decay chain
> by using madspin. However it gives me the following error:
>
> Error detected in "generate_events run_02"
> write debug file /home/jack/packages/MG5_aMC_v2_4_0/chachabar/run_02_tag_2_debug.log
> If you need help with this issue please contact us on https://answers.launchpad.net/mg5amcnlo
> MadGraph5Error : h3 particles with pdg code 45 is in conflict with MG convention name for particle 36.
> Use -modelname in order to use the particles name defined in the model and not the MadGraph5_aMC@NLO convention
>
> The problem is I'm already importing the model by using 'import model
> $model --modelname' which generated by SARAH and masses and decay
> tables were calculated by SPheno with proper flags for madgraph. I
> also tried to run it directly from madspin itself instead of launching
> it from mg5, however it gave me the same error all the time. Is there
> any way to fix this?
>
> Thanks
>
> Best regards
> Jack
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/mg5amcnlo/+bug/1596226/+subscriptions

Revision history for this message
Jack Y. Araz (jackaraz) wrote :

Hi Oliver

Sorry for the trouble but I erased all the comments tried different indentations but its still not working and I really dont understand why, can you possibly upload your madgraph_interface.py file or copy that part which shows the exact indentation because I can not think any other possibilities. Thanks

Best regards
Jack

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

This is the madgraph_interface.py corresponding to version 2.4.3.
It might not be fully equivalent to the one present in your version of madgraph.
But the part close to the patch should be identical and show you how to modify the code.

Revision history for this message
Jack Y. Araz (jackaraz) wrote :

Hi Oliver

So I got one step further, now madspin can understand the model and shows me all the decay channels for the particles when I launch, however it still stops at h3 and quits the program with the same error. I'm adding my param card maybe its due to something in my param card I don't understand really why it works for you but not for me. I copied exact lines from the file that you sent above, it prints them same as you said but it doesn't proceed after h3.

Sorry for taking so much time, thank you very much.

Best regards
Jack

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

Hi,

I would actually also need your proc_card, madspin_card,…
I was not able to fully test your process, since I do not know which process/decay you
are trying to do.
So I stop my test after the successful loading of the model.

Cheers,

Olivier

PS: Note that loop-induced decay are not supported in MadSpin.

> On Jun 27, 2016, at 18:07, jackaraz <email address hidden> wrote:
>
> Hi Oliver
>
> So I got one step further, now madspin can understand the model and
> shows me all the decay channels for the particles when I launch, however
> it still stops at h3 and quits the program with the same error. I'm
> adding my param card maybe its due to something in my param card I don't
> understand really why it works for you but not for me. I copied exact
> lines from the file that you sent above, it prints them same as you said
> but it doesn't proceed after h3.
>
> Sorry for taking so much time, thank you very much.
>
> Best regards
> Jack
>
> ** Attachment added: "param card"
> https://bugs.launchpad.net/mg5amcnlo/+bug/1596226/+attachment/4691188/+files/param_card.dat
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1596226
>
> Title:
> --modelname with madspin
>
> Status in MadGraph5_aMC@NLO:
> New
>
> Bug description:
> Hi
>
> I'm trying to calculate cross section of a process with a decay chain
> by using madspin. However it gives me the following error:
>
> Error detected in "generate_events run_02"
> write debug file /home/jack/packages/MG5_aMC_v2_4_0/chachabar/run_02_tag_2_debug.log
> If you need help with this issue please contact us on https://answers.launchpad.net/mg5amcnlo
> MadGraph5Error : h3 particles with pdg code 45 is in conflict with MG convention name for particle 36.
> Use -modelname in order to use the particles name defined in the model and not the MadGraph5_aMC@NLO convention
>
> The problem is I'm already importing the model by using 'import model
> $model --modelname' which generated by SARAH and masses and decay
> tables were calculated by SPheno with proper flags for madgraph. I
> also tried to run it directly from madspin itself instead of launching
> it from mg5, however it gave me the same error all the time. Is there
> any way to fix this?
>
> Thanks
>
> Best regards
> Jack
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/mg5amcnlo/+bug/1596226/+subscriptions

Revision history for this message
Jack Y. Araz (jackaraz) wrote :

Hi

Sure you can find param card above, I tried p p > n1 n1, n1 > sv1 nu3* or p p > c1 c1bar, c1 > n1 wm, wm > lep neut. none of these working

for instance one madspin card is as follows

decay n1 > nu3 sv1c
decay n1 > nu3bar sv1
# running the actual code
launch

proc_card:

import model UMSSM -modelname
define lep = l+ l-
define neut = vl vl~
define neut3 = nu3 nu3bar
define w = wmc wm
define dm = sv1 sv1c
generate p p > n1 n1
output chi1_test

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

Hi,

here is a patch:

Revision history for this message
Jack Y. Araz (jackaraz) wrote :

Hi Oliver

Sorry but its still not working, I checked everything that you wrote me to change. I even tried to generate process with decay chain such as

> generate p p > n1 n1, n1 > neut3 dm, n1 > neut3 dm

Note that when I put parenthesis madspin didnt recognised n1 and with this it still gives me the same h3 error.

Best regards

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

Hi,

With what I see from your debug file, you did not apply the patch correctly.

Cheers,

Olivier
> On Jun 28, 2016, at 03:00, jackaraz <email address hidden> wrote:
>
> Hi Oliver
>
> Sorry but its still not working, I checked everything that you wrote me
> to change. I even tried to generate process with decay chain such as
>
>> generate p p > n1 n1, n1 > neut3 dm, n1 > neut3 dm
>
> Note that when I put parenthesis madspin didnt recognised n1 and with
> this it still gives me the same h3 error.
>
> Best regards
>
> ** Attachment added: "debug file"
> https://bugs.launchpad.net/mg5amcnlo/+bug/1596226/+attachment/4691357/+files/run_01_tag_2_debug.log
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1596226
>
> Title:
> --modelname with madspin
>
> Status in MadGraph5_aMC@NLO:
> New
>
> Bug description:
> Hi
>
> I'm trying to calculate cross section of a process with a decay chain
> by using madspin. However it gives me the following error:
>
> Error detected in "generate_events run_02"
> write debug file /home/jack/packages/MG5_aMC_v2_4_0/chachabar/run_02_tag_2_debug.log
> If you need help with this issue please contact us on https://answers.launchpad.net/mg5amcnlo
> MadGraph5Error : h3 particles with pdg code 45 is in conflict with MG convention name for particle 36.
> Use -modelname in order to use the particles name defined in the model and not the MadGraph5_aMC@NLO convention
>
> The problem is I'm already importing the model by using 'import model
> $model --modelname' which generated by SARAH and masses and decay
> tables were calculated by SPheno with proper flags for madgraph. I
> also tried to run it directly from madspin itself instead of launching
> it from mg5, however it gave me the same error all the time. Is there
> any way to fix this?
>
> Thanks
>
> Best regards
> Jack
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/mg5amcnlo/+bug/1596226/+subscriptions

Revision history for this message
Jack Y. Araz (jackaraz) wrote :

Hi Oliver

I'm afraid I do not see the mistake that I have done, I basically copied what you have sent

decay.py: line 2653-2666

        mgcmd = self.mgcmd
        modelpath = self.model.get('modelpath')
        if os.path.basename(modelpath) != mgcmd._curr_model['name']:
            name, restrict = mgcmd._curr_model['name'].rsplit('-',1)
            if os.path.exists(pjoin(os.path.dirname(modelpath),name, 'restrict_%s.dat' % restrict)):
                modelpath = pjoin(os.path.dirname(modelpath), mgcmd._curr_model['name'])
        modelpath = self.model.get('modelpath+restriction')

        commandline="import model %s" % modelpath
        if not self.model.mg5_name:
            commandline += ' --modelname'

        commandline="import model %s " % modelpath
        mgcmd.exec_cmd(commandline)

base_objects.py: line 1021-1028

class Model(PhysicsObject):
    """A class to store all the model information."""

    mg5_name = False #store if particle name follow mg5 convention

    def default_setup(self):

        self['name'] = ""

line 1429 - 1440:

        self['ref_dict_to1'] = {}
        self['ref_dict_to0'] = {}

    def pass_particles_name_in_mg_default(self):
        """Change the name of the particles such that all SM and MSSM particles
        follows the MG convention"""

        self.mg5_name = True

        # Check that default name/antiname is not already use
        def check_name_free(self, name):
            """ check if name is not use for a particle in the model if it is

There is also 1045-1047 but its only an empty line, only thing that I observed, on the other hand, there is a shift in the number of lines. Sorry for taking your time. Thanks a lot for your patience.

Best regards
Jack

Revision history for this message
Olivier Mattelaer (olivier-mattelaer) wrote :
Download full text (3.8 KiB)

Hi,

It would have bee easier to use the program patch to apply those changes automatically. but ok.
( that program is insensitive to the line number which is simply due to the fact that I implement the patch in the development version)

Your problem is simple, you have kept the line
> commandline=“import model %s “ % modelpath
after the new line
> commandline="import model %s" % modelpath
> if not self.model.mg5_name:
> commandline += ' --modelname'

Cheers,

Olivier

> On Jun 28, 2016, at 16:10, jackaraz <email address hidden> wrote:
>
> Hi Oliver
>
> I'm afraid I do not see the mistake that I have done, I basically copied
> what you have sent
>
> decay.py: line 2653-2666
>
> mgcmd = self.mgcmd
> modelpath = self.model.get('modelpath')
> if os.path.basename(modelpath) != mgcmd._curr_model['name']:
> name, restrict = mgcmd._curr_model['name'].rsplit('-',1)
> if os.path.exists(pjoin(os.path.dirname(modelpath),name, 'restrict_%s.dat' % restrict)):
> modelpath = pjoin(os.path.dirname(modelpath), mgcmd._curr_model['name'])
> modelpath = self.model.get('modelpath+restriction')
>
> commandline="import model %s" % modelpath
> if not self.model.mg5_name:
> commandline += ' --modelname'
>
> commandline="import model %s " % modelpath
> mgcmd.exec_cmd(commandline)
>
> base_objects.py: line 1021-1028
>
> class Model(PhysicsObject):
> """A class to store all the model information."""
>
> mg5_name = False #store if particle name follow mg5 convention
>
> def default_setup(self):
>
> self['name'] = ""
>
>
> line 1429 - 1440:
>
> self['ref_dict_to1'] = {}
> self['ref_dict_to0'] = {}
>
> def pass_particles_name_in_mg_default(self):
> """Change the name of the particles such that all SM and MSSM particles
> follows the MG convention"""
>
> self.mg5_name = True
>
> # Check that default name/antiname is not already use
> def check_name_free(self, name):
> """ check if name is not use for a particle in the model if it is
>
>
> There is also 1045-1047 but its only an empty line, only thing that I observed, on the other hand, there is a shift in the number of lines. Sorry for taking your time. Thanks a lot for your patience.
>
> Best regards
> Jack
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1596226
>
> Title:
> --modelname with madspin
>
> Status in MadGraph5_aMC@NLO:
> New
>
> Bug description:
> Hi
>
> I'm trying to calculate cross section of a process with a decay chain
> by using madspin. However it gives me the following error:
>
> Error detected in "generate_events run_02"
> write debug file /home/jack/packages/MG5_aMC_v2_4_0/chachabar/run_02_tag_2_debug.log
> If you need help with this issue please contact us on https://answers.launchpad.net/mg5amcnlo
> MadGraph5Error : h3 particles with pdg code 45 is in conflict with MG convention name ...

Read more...

Revision history for this message
Jack Y. Araz (jackaraz) wrote :

Hi

Thanks a lot Oliver, it solved the problem for p p > n1 n1 > ... but when I ran p p > w w > 2lep 2neut it tries to use madwidth and gives me the very same error again. I'm basically using

generate p p > w w

madspin:
decay w > lep neut
launch

and same for the rest. Sorry for taking your time and thank you very much for your help

Best regards
Jack

Changed in mg5amcnlo:
status: New → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Related questions

Remote bug watches

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