can't generate anything with new model, KeyError: 1

Asked by Kara Farnsworth

load MG5 configuration from input/mg5_configuration.txt
Using default text editor "vi". Set another one in ./input/mg5_configuration.txt
Loading default model: sm
INFO: load particles
INFO: load vertices
INFO: Restrict model sm with file models/sm/restrict_default.dat .
INFO: Run "set stdout_level DEBUG" before import for more information.
INFO: Change particles name to pass to MG5 convention
Defined multiparticle p = g u c d s u~ c~ d~ s~
Defined multiparticle j = g u c d s u~ c~ d~ s~
Defined multiparticle l+ = e+ mu+
Defined multiparticle l- = e- mu-
Defined multiparticle vl = ve vm vt
Defined multiparticle vl~ = ve~ vm~ vt~
Defined multiparticle all = g u c d s u~ c~ d~ s~ a ve vm vt e- mu- ve~ vm~ vt~ e+ mu+ t b t~ b~ z w+ h w- ta- ta+
mg5>import model LSM_UFO
INFO: load particles
INFO: load vertices
INFO: Change particles name to pass to MG5 convention
Kept definitions of multiparticles l- / j / vl / l+ / p / vl~ unchanged
Defined multiparticle all = g u c d s u~ c~ d~ s~ a p+ p0 p- ve vm vt e- mu- ve~ vm~ vt~ e+ mu+ t b t~ b~ z w+ h sigma ps w- ta- ta+
mg5>generate p p > Z
INFO: Checking for minimal orders which gives processes.
INFO: Please specify coupling orders to bypass this step.
Command "generate p p > Z" interrupted with error:
KeyError : '1'
Please report this bug on https://bugs.launchpad.net/madgraph5
More information is found in 'MG5_debug'.
Please attach this file to your report.
mg5>generate Z > l+ l-
INFO: Trying process: z > e+ e-
INFO: Process has 1 diagrams
INFO: Trying process: z > e+ mu-
INFO: Trying process: z > mu+ e-
INFO: Trying process: z > mu+ mu-
INFO: Process has 1 diagrams
2 processes with 2 diagrams generated in 0.046 s
Total: 2 processes with 2 diagrams
mg5>

It works for some processes (mostly decays) but not others. I made a UFO file using Feynrules. I'm not sure what "KeyError: '1'" means. Thank you!

Kara

Question information

Language:
English Edit question
Status:
Solved
For:
MadGraph5_aMC@NLO Edit question
Assignee:
No assignee Edit question
Solved by:
Olivier Mattelaer
Solved:
Last query:
Last reply:
Revision history for this message
Kara Farnsworth (kmfarnsworth) said :
#1
Revision history for this message
Best Olivier Mattelaer (olivier-mattelaer) said :
#2

Usually, this means that the orders of your model is not correctly define and that some of your couplings have an order set at '1'.
(while it should be QCD/QED/...)
When this is the case, FR didn't define that coupling in the coupling_orders.py.

Please submit a ticket on the FR team, if you don't know how to solve this problem.
(https://feynrules.irmp.ucl.ac.be/newticket)

If this is not the case, you can send me your UFO model and I will investigate. (<email address hidden>)

Cheers,

Olivier

Revision history for this message
Kara Farnsworth (kmfarnsworth) said :
#3

Thanks Olivier Mattelaer, that solved my question.