--modelname with madspin
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/
If you need help with this issue please contact us on https:/
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
Olivier Mattelaer (olivier-mattelaer) wrote : | #1 |
Jack Y. Araz (jackaraz) wrote : | #2 |
- model attachment Edit (3.2 MiB, application/x-tar)
Hi Oliver
model file is attached and I'm also including debug file below. Thanks a lot
jack
run_01_
generate_events run_01
Traceback (most recent call last):
File "/home/
return self.onecmd_
File "/home/
return func(arg, **opt)
File "/home/
self.
File "/home/
stop = Cmd.onecmd_
File "/home/
return func(arg, **opt)
File "/home/
madspin_cmd = interface_
File "/home/
out = f(self, *args, **opt)
File "/home/
self.
File "/home/
self.
File "/home/
stop = Cmd.onecmd_
File "/home/
return func(arg, **opt)
File "/home/
return self.cmd.
File "/home/
MadGraphCmd
File "/home/
self.
File "/home/
check_
File "/home/
(part.
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
automatic_
Olivier Mattelaer (olivier-mattelaer) wrote : Re: [Bug 1596226] --modelname with madspin | #3 |
Thanks to you to report this bug, this allow us to fix it.
Here is the patch:
=== modified file 'madgraph/
--- madgraph/
+++ madgraph/
@@ -6762,6 +6762,11 @@
+
+ if self.options[
+ return
+
+
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_
>
> generate_events run_01
> Traceback (most recent call last):
> File "/home/
> return self.onecmd_
> File "/home/
> return func(arg, **opt)
> File "/home/
> self.exec_
> File "/home/
> stop = Cmd.onecmd_
> File "/home/
> return func(arg, **opt)
> File "/home/
> madspin_cmd = interface_
> File "/home/
> out = f(self, *args, **opt)
> File "/home/
> self.do_
> File "/home/
> self.mg5cmd.
> File "/home/
> stop = Cmd.onecmd_
> File "/home/
> return func(arg, **opt)
> File "/home/
> return self.cmd.
> File "/home/
> MadGraphCmd.
> File "/home/
> self._curr_
> File "/home/
Jack Y. Araz (jackaraz) wrote : | #4 |
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/
return self.onecmd_
File "/home/
return func(arg, **opt)
File "/home/
self.
File "/home/
stop = Cmd.onecmd_
File "/home/
return func(arg, **opt)
File "/home/
return self.cmd.
File "/home/
MadGraphCmd
File "/home/
self.
File "/home/
check_
File "/home/
(part.
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:
max_
Nevents_
max_
Olivier Mattelaer (olivier-mattelaer) wrote : | #5 |
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[
(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/
> return self.onecmd_
> File "/home/
> return func(arg, **opt)
> File "/home/
> self.mg5cmd.
> File "/home/
> stop = Cmd.onecmd_
> File "/home/
> return func(arg, **opt)
> File "/home/
> return self.cmd.
> File "/home/
> MadGraphCmd.
> File "/home/
> self._curr_
> File "/home/
> check_name_
> File "/home/
> (part.get_name(), part.get_
> 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_
> BW_cut : 15.0
> use_old_dir : False
> max_weight : -1
> curr_dir : /home/jack/
> ms_dir : None
> max_running_process : 100
>
...
Jack Y. Araz (jackaraz) wrote : | #6 |
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.
File "/home/
import madgraph.
File "/home/
SyntaxError: Non-ASCII character '\xe2' in file /home/jack/
Olivier Mattelaer (olivier-mattelaer) wrote : | #7 |
Hi,
> SyntaxError: Non-ASCII character ‘\xe2' in file /home/jack/
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.
> File "/home/
> import madgraph.
> File "/home/
> SyntaxError: Non-ASCII character '\xe2' in file /home/jack/
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https:/
>
> 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/
> If you need help with this issue please contact us on https:/
> 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:/
Jack Y. Araz (jackaraz) wrote : | #8 |
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_
Best regards
Jack
Olivier Mattelaer (olivier-mattelaer) wrote : | #9 |
- madgraph_interface.py Edit (385.2 KiB, text/x-python)
This is the madgraph_
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.
Jack Y. Araz (jackaraz) wrote : | #10 |
- param card Edit (77.9 KiB, application/x-ns-proxy-autoconfig)
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
Olivier Mattelaer (olivier-mattelaer) wrote : | #11 |
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:/
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https:/
>
> 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/
> If you need help with this issue please contact us on https:/
> 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:/
Jack Y. Araz (jackaraz) wrote : | #12 |
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
Olivier Mattelaer (olivier-mattelaer) wrote : | #13 |
Jack Y. Araz (jackaraz) wrote : | #14 |
- debug file Edit (6.3 KiB, text/plain)
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
Olivier Mattelaer (olivier-mattelaer) wrote : | #15 |
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:/
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https:/
>
> 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/
> If you need help with this issue please contact us on https:/
> 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:/
Jack Y. Araz (jackaraz) wrote : | #16 |
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.
if os.path.
name, restrict = mgcmd._
if os.path.
modelpath = self.model.
if not self.model.
base_objects.py: line 1021-1028
class Model(PhysicsOb
"""A class to store all the model information."""
mg5_name = False #store if particle name follow mg5 convention
def default_
line 1429 - 1440:
def pass_particles_
"""Change the name of the particles such that all SM and MSSM particles
follows the MG convention"""
# Check that default name/antiname is not already use
def check_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
Olivier Mattelaer (olivier-mattelaer) wrote : | #17 |
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.
> 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.
> if os.path.
> name, restrict = mgcmd._
> if os.path.
> modelpath = pjoin(os.
> modelpath = self.model.
>
> commandline="import model %s" % modelpath
> if not self.model.
> commandline += ' --modelname'
>
> commandline="import model %s " % modelpath
> mgcmd.exec_
>
> base_objects.py: line 1021-1028
>
> class Model(PhysicsOb
> """A class to store all the model information."""
>
> mg5_name = False #store if particle name follow mg5 convention
>
> def default_
>
> self['name'] = ""
>
>
> line 1429 - 1440:
>
> self['ref_
> self['ref_
>
> def pass_particles_
> """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_
> """ 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:/
>
> 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/
> If you need help with this issue please contact us on https:/
> MadGraph5Error : h3 particles with pdg code 45 is in conflict with MG convention name ...
Jack Y. Araz (jackaraz) wrote : | #18 |
- debug file Edit (6.9 KiB, text/plain)
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 |
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