Problem in Pythia output for multiparticle vertices -- fixed
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
MadGraph5_aMC@NLO |
Fix Released
|
Undecided
|
Johan Alwall |
Bug Description
Hi,
I'm trying to plug a new model with Feynrules/
The first message occurs when I try a e+ e- > s1+ s1- (Scalars) process:
Command "output pythia8" interrupted with error:
AttributeError : 'NoneType' object has no attribute 'get'
Please report this bug on https:/
More information is found in 'MG5_debug'.
Please attach this file to your report.
The second message occurs when I try a e+ e- > e+ e- Process (as test):
Command "output pythia8" interrupted with error:
KeyError : ('FFSS1', 4)
Please report this bug on https:/
More information is found in 'MG5_debug'.
Please attach this file to your report.
For the second there was a bug #861263, which is marked as solved. So I am nor sure if this is a question or a bug.
The Debug for the first is:
Traceback (most recent call last):
File "/net/home/
return cmd.Cmd.
File "/usr/lib/
return func(arg)
File "/net/home/
return self.cmd.
File "/net/home/
self.
File "/net/home/
process_number = group_number, path = path)
File "/net/home/
process_
File "/net/home/
self.
File "/net/home/
process_
File "/net/home/
replace_
File "/net/home/
sids, singleres, schannel = self.get_
File "/net/home/
width = self.model.
AttributeError: 'NoneType' object has no attribute 'get'
For the second:
Traceback (most recent call last):
File "/net/home/
return cmd.Cmd.
File "/usr/lib/
return func(arg)
File "/net/home/
return self.cmd.
File "/net/home/
self.
File "/net/home/
self.
File "/net/home/
model_
File "/net/home/
self.
File "/net/home/
aloha_
File "/net/home/
self[
KeyError: ('FFSS1', 4)
Changed in madgraph5: | |
status: | Fix Committed → Fix Released |
summary: |
- Problem in Pythia output for multiparticle vertices + Problem in Pythia output for multiparticle vertices -- fixed |
In fact, this was two bugs, one for the Pythia 8 matrix element output and one for the C++ ALOHA output. Both will be fixed in upcoming v. 1.4.6.
Many thanks MoritzHuck for reporting this.
All the best,
Johan