Error running madspin - KeyError : ((-5, 21), (-6, -5, 6))

Asked by Anna Ivina on 2018-10-02

Hello,

I have encountered a problem and I am not sure how to resolve this.
I am trying to do the following process in MadSpin:

p p > t t~, (t~ > b~ w- , w- > l- vl~ ), t > b h+

I am using the 2HDMtypeII model for this purpose.

I have an error as follows

Command "launch" interrupted with error:
KeyError : ((-5, 21), (-6, -5, 6))
Please report this bug to developers
More information is found in 'MS_debug'.
Please attach this file to your report.

It would be very greate if you would help me to resolve this problem.
Thank you!
Anna

My Madspin card:

set Nevents_for_max_weigth 100 # number of events for the estimate of the max. weight (default: 75)
set max_weight_ps_point 1000 # number of PS to estimate the maximum for each event (default: 400)
set seed 765432
import run.lhe
set ms_dir MadSpin
define l+ = e+ mu+ ta+
define l- = e- mu- ta-
define vl = ve vm vt
define vl~ = ve~ vm~ vt~
define p = g u c d s u~ c~ d~ s~
define j = g u c d s u~ c~ d~ s~

decay t > b h+
decay t~ > b~ w-, w- > l- vl~
launch

My param_card:
###################################
## INFORMATION FOR MASS
###################################
Block mass
    6 1.725000e+02 # MT
   23 9.118760e+01 # MZ
   25 125.0 # mh1 #
    5 4.700000e+00 # MB
    4 1.550000e+00 # MC
   35 179.064232054 # mh2 #
   36 179.064232054 # mh2 #
   37 160 # mhc #
## Dependent parameters, given by model restrictions.
## Those values should be edited following the
## analytical expression. MG5 ignores those values
## but they are important for interfacing the output of MG5
## to external program such as Pythia.
  1 0.000000 # d : 0.0
  2 0.000000 # u : 0.0
  3 0.000000 # s : 0.0
# 4 0.000000 # c : 0.0
# 5 0.000000 # b : 0.0
  11 0.000000 # e- : 0.0
  12 0.000000 # ve : 0.0
  13 0.000000 # mu- : 0.0
  14 0.000000 # vm : 0.0
  15 0.000000 # ta- : 0.0
  16 0.000000 # vt : 0.0
  21 0.000000 # g : 0.0
  22 0.000000 # a : 0.0
  24 80.39900 # w+ : cmath.sqrt(MZ__exp__2/2. + cmath.sqrt(MZ__exp__4/4. - (aEW*cmath.pi*MZ__exp__2)/(Gf*sqrt__2)))
  82 0.000000 # ghg : 0.0

###################################
## INFORMATION FOR SMINPUTS
###################################
Block sminputs
    1 1.279000e+02 # aEWM1
    2 1.166390e-05 # Gf
    3 1.180000e-01 # aS

###################################
## INFORMATION FOR YUKAWA
###################################
Block yukawa
    1 5.040000e-03 # ymdo
    2 2.550000e-03 # ymup
    3 1.010000e-01 # yms
    4 1.270000e+00 # ymc
    5 4.700000e+00 # ymb
    6 1.725000e+02 # ymt
   11 5.110000e-04 # yme
   13 1.056600e-01 # ymm
   15 1.777000e+00 # ymtau

###################################
## INFORMATION FOR DECAY
###################################
#DECAY 6 1.508336e+00 # WT
DECAY 23 2.495200e+00 # WZ
#DECAY 24 2.085000e+00 # WW
DECAY 25 1.000000e+00
DECAY 35 1.000000e+00
DECAY 36 1.000000e+00
DECAY 37 1.300000e+02 # whc
Block FRBlock
    1 2.000000e+01 # beta
## Dependent parameters, given by model restrictions.
## Those values should be edited following the
## analytical expression. MG5 ignores those values
## but they are important for interfacing the output of MG5
## to external program such as Pythia.
DECAY 1 0.000000 # d : 0.0
DECAY 2 0.000000 # u : 0.0
DECAY 3 0.000000 # s : 0.0
DECAY 4 0.000000 # c : 0.0
DECAY 5 0.000000 # b : 0.0
DECAY 11 0.000000 # e- : 0.0
DECAY 12 0.000000 # ve : 0.0
DECAY 13 0.000000 # mu- : 0.0
DECAY 14 0.000000 # vm : 0.0
DECAY 15 0.000000 # ta- : 0.0
DECAY 16 0.000000 # vt : 0.0
DECAY 21 0.000000 # g : 0.0
DECAY 22 0.000000 # a : 0.0
DECAY 82 0.000000 # ghg : 0.0
DECAY 9000001 0.000000 # gha : 0.0
DECAY 9000002 2.495200 # ghz : WZ
DECAY 9000003 2.085000 # ghwp : WW
DECAY 9000004 2.085000 # ghwm : WW

## DECAY ID WIDTH
## NDA ID1 ID2 ...
DECAY -24 2.085000e+00
      3.377e-01 2 1 -2
      3.377e-01 2 3 -4
      1.082e-01 2 11 -12
      1.082e-01 2 13 -14
      1.082e-01 2 15 -16
DECAY 24 2.085000e+00
      3.377e-01 2 -1 2
      3.377e-01 2 -3 4
      1.082e-01 2 -11 12
      1.082e-01 2 -13 14
      1.082e-01 2 -15 16

#With this, I can have small couplings to be consistent
# with the SM width and limit on BR (~ 0.1%), and yet generate the exotic width
#
DECAY -6 1.33
       9.96e-01 2 -5 -24
       0.10e-02 2 -4 25
       0.10e-02 2 -2 25
       0.05e-02 2 -4 23
       0.05e-02 2 -2 23
       0.05e-02 2 -4 22
       0.05e-02 2 -2 22
       0.05e-02 2 -5 -37

DECAY 6 1.33
      9.96e-01 2 5 24
      0.10e-02 2 4 25
      0.10e-02 2 2 25
      0.05e-02 2 4 23
      0.05e-02 2 2 23
      0.05e-02 2 4 22
      0.05e-02 2 2 22
      0.05e-02 2 5 37

###################################
## INFORMATION FOR HIGGS
###################################
Block Higgs
    1 5.000000e-01 # l2
    2 1.000000e+00 # l3
    3 0.000000e+00 # lR7
    5 3.000000e-01 # mixh

###################################
## INFORMATION FOR LOOP
###################################
Block LOOP
    1 9.118800e+01 # MU_R

#===========================================================
# QUANTUM NUMBERS OF NEW STATE(S) (NON SM PDG CODE)
#===========================================================

Block QNUMBERS 9000001 # gha
        1 0 # 3 times electric charge
        2 1 # number of spin states (2S+1)
        3 1 # colour rep (1: singlet, 3: triplet, 8: octet)
        4 1 # Particle/Antiparticle distinction (0=own anti)
Block QNUMBERS 9000002 # ghz
        1 0 # 3 times electric charge
        2 1 # number of spin states (2S+1)
        3 1 # colour rep (1: singlet, 3: triplet, 8: octet)
        4 1 # Particle/Antiparticle distinction (0=own anti)
Block QNUMBERS 9000003 # ghwp
        1 3 # 3 times electric charge
        2 1 # number of spin states (2S+1)
        3 1 # colour rep (1: singlet, 3: triplet, 8: octet)
        4 1 # Particle/Antiparticle distinction (0=own anti)
Block QNUMBERS 9000004 # ghwm
        1 -3 # 3 times electric charge
        2 1 # number of spin states (2S+1)
        3 1 # colour rep (1: singlet, 3: triplet, 8: octet)
        4 1 # Particle/Antiparticle distinction (0=own anti)
Block QNUMBERS 82 # ghg
        1 0 # 3 times electric charge
        2 1 # number of spin states (2S+1)
        3 8 # colour rep (1: singlet, 3: triplet, 8: octet)
        4 1 # Particle/Antiparticle distinction (0=own anti)
Block QNUMBERS 37 # h+
        1 3 # 3 times electric charge
        2 1 # number of spin states (2S+1)
        3 1 # colour rep (1: singlet, 3: triplet, 8: octet)
        4 1 # Particle/Antiparticle distinction (0=own anti)
Block QNUMBERS 35 # h2
        1 0 # 3 times electric charge
        2 1 # number of spin states (2S+1)
        3 1 # colour rep (1: singlet, 3: triplet, 8: octet)
        4 0 # Particle/Antiparticle distinction (0=own anti)
Block QNUMBERS 36 # h3
        1 0 # 3 times electric charge
        2 1 # number of spin states (2S+1)
        3 1 # colour rep (1: singlet, 3: triplet, 8: octet)
        4 0 # Particle/Antiparticle distinction (0=own anti)

My MS_debug report:
set Nevents_for_max_weigth 100
set max_weight_ps_point 1000
set seed 765432
import run.lhe
set ms_dir MadSpin
define l+ = e+ mu+ ta+
define l- = e- mu- ta-
define vl = ve vm vt
define vl~ = ve~ vm~ vt~
define p = g u c d s u~ c~ d~ s~
define j = g u c d s u~ c~ d~ s~
decay t > b h+
decay t~ > b~ w-, w- > l- vl~
launch
Traceback (most recent call last):
  File "/cvmfs/atlas.cern.ch/repo/sw/software/x86_64-slc6-gcc47-opt/19.2.5/sw/lcg/external/MCGenerators_lcgcmt67c/madgraph5amc/2.6.2.atlas2/x86_64-slc6-gcc47-opt/madgraph/interface/extended_cmd.py", line 1501, in onecmd
    return self.onecmd_orig(line, **opt)
  File "/cvmfs/atlas.cern.ch/repo/sw/software/x86_64-slc6-gcc47-opt/19.2.5/sw/lcg/external/MCGenerators_lcgcmt67c/madgraph5amc/2.6.2.atlas2/x86_64-slc6-gcc47-opt/madgraph/interface/extended_cmd.py", line 1450, in onecmd_orig
    return func(arg, **opt)
  File "/cvmfs/atlas.cern.ch/repo/sw/software/x86_64-slc6-gcc47-opt/19.2.5/sw/lcg/external/MCGenerators_lcgcmt67c/madgraph5amc/2.6.2.atlas2/x86_64-slc6-gcc47-opt/madgraph/various/misc.py", line 100, in f_with_no_logger
    out = f(self, *args, **opt)
  File "/cvmfs/atlas.cern.ch/repo/sw/software/x86_64-slc6-gcc47-opt/19.2.5/sw/lcg/external/MCGenerators_lcgcmt67c/madgraph5amc/2.6.2.atlas2/x86_64-slc6-gcc47-opt/MadSpin/interface_madspin.py", line 582, in do_launch
    generate_all.run()
  File "/cvmfs/atlas.cern.ch/repo/sw/software/x86_64-slc6-gcc47-opt/19.2.5/sw/lcg/external/MCGenerators_lcgcmt67c/madgraph5amc/2.6.2.atlas2/x86_64-slc6-gcc47-opt/MadSpin/decay.py", line 2118, in run
    self.get_max_weight_from_event(decay_mapping)
  File "/cvmfs/atlas.cern.ch/repo/sw/software/x86_64-slc6-gcc47-opt/19.2.5/sw/lcg/external/MCGenerators_lcgcmt67c/madgraph5amc/2.6.2.atlas2/x86_64-slc6-gcc47-opt/MadSpin/decay.py", line 3110, in get_max_weight_from_event
    production_tag, event_map = self.load_event()
  File "/cvmfs/atlas.cern.ch/repo/sw/software/x86_64-slc6-gcc47-opt/19.2.5/sw/lcg/external/MCGenerators_lcgcmt67c/madgraph5amc/2.6.2.atlas2/x86_64-slc6-gcc47-opt/MadSpin/decay.py", line 3249, in load_event
    P_order = self.all_ME[production_tag]['tag2order'][production_tag]
KeyError: ((-5, 21), (-6, -5, 6))
Value of current Options:
                 spinmode : madspin
             onlyhelicity : False
                     seed : 765432
      max_weight_ps_point : 1000
              fixed_order : False
                 nb_sigma : 0
                 run_card : None
   Nevents_for_max_weigth : 100
                   BW_cut : 50.0
              use_old_dir : False
               max_weight : -1
                 curr_dir : MadSpin
                   ms_dir : MadSpin
      max_running_process : 100

Question information

Language:
English Edit question
Status:
Answered
For:
MadGraph5_aMC@NLO Edit question
Assignee:
No assignee Edit question
Last query:
2018-10-04
Last reply:
2018-10-04

Did you try the latest version?

Cheers,

Olivier

> On 2 Oct 2018, at 09:13, Anna Ivina <email address hidden> wrote:
>
> New question #674585 on MadGraph5_aMC@NLO:
> https://answers.launchpad.net/mg5amcnlo/+question/674585
>
> Hello,
>
> I have encountered a problem and I am not sure how to resolve this.
> I am trying to do the following process in MadSpin:
>
> p p > t t~, (t~ > b~ w- , w- > l- vl~ ), t > b h+
>
> I am using the 2HDMtypeII model for this purpose.
>
> I have an error as follows
>
> Command "launch" interrupted with error:
> KeyError : ((-5, 21), (-6, -5, 6))
> Please report this bug to developers
> More information is found in 'MS_debug'.
> Please attach this file to your report.
>
>
> It would be very greate if you would help me to resolve this problem.
> Thank you!
> Anna
>
>
> My Madspin card:
>
> set Nevents_for_max_weigth 100 # number of events for the estimate of the max. weight (default: 75)
> set max_weight_ps_point 1000 # number of PS to estimate the maximum for each event (default: 400)
> set seed 765432
> import run.lhe
> set ms_dir MadSpin
> define l+ = e+ mu+ ta+
> define l- = e- mu- ta-
> define vl = ve vm vt
> define vl~ = ve~ vm~ vt~
> define p = g u c d s u~ c~ d~ s~
> define j = g u c d s u~ c~ d~ s~
>
>
>
> decay t > b h+
> decay t~ > b~ w-, w- > l- vl~
> launch
>
> My param_card:
> ###################################
> ## INFORMATION FOR MASS
> ###################################
> Block mass
> 6 1.725000e+02 # MT
> 23 9.118760e+01 # MZ
> 25 125.0 # mh1 #
> 5 4.700000e+00 # MB
> 4 1.550000e+00 # MC
> 35 179.064232054 # mh2 #
> 36 179.064232054 # mh2 #
> 37 160 # mhc #
> ## Dependent parameters, given by model restrictions.
> ## Those values should be edited following the
> ## analytical expression. MG5 ignores those values
> ## but they are important for interfacing the output of MG5
> ## to external program such as Pythia.
> 1 0.000000 # d : 0.0
> 2 0.000000 # u : 0.0
> 3 0.000000 # s : 0.0
> # 4 0.000000 # c : 0.0
> # 5 0.000000 # b : 0.0
> 11 0.000000 # e- : 0.0
> 12 0.000000 # ve : 0.0
> 13 0.000000 # mu- : 0.0
> 14 0.000000 # vm : 0.0
> 15 0.000000 # ta- : 0.0
> 16 0.000000 # vt : 0.0
> 21 0.000000 # g : 0.0
> 22 0.000000 # a : 0.0
> 24 80.39900 # w+ : cmath.sqrt(MZ__exp__2/2. + cmath.sqrt(MZ__exp__4/4. - (aEW*cmath.pi*MZ__exp__2)/(Gf*sqrt__2)))
> 82 0.000000 # ghg : 0.0
>
> ###################################
> ## INFORMATION FOR SMINPUTS
> ###################################
> Block sminputs
> 1 1.279000e+02 # aEWM1
> 2 1.166390e-05 # Gf
> 3 1.180000e-01 # aS
>
> ###################################
> ## INFORMATION FOR YUKAWA
> ###################################
> Block yukawa
> 1 5.040000e-03 # ymdo
> 2 2.550000e-03 # ymup
> 3 1.010000e-01 # yms
> 4 1.270000e+00 # ymc
> 5 4.700000e+00 # ymb
> 6 1.725000e+02 # ymt
> 11 5.110000e-04 # yme
> 13 1.056600e-01 # ymm
> 15 1.777000e+00 # ymtau
>
> ###################################
> ## INFORMATION FOR DECAY
> ###################################
> #DECAY 6 1.508336e+00 # WT
> DECAY 23 2.495200e+00 # WZ
> #DECAY 24 2.085000e+00 # WW
> DECAY 25 1.000000e+00
> DECAY 35 1.000000e+00
> DECAY 36 1.000000e+00
> DECAY 37 1.300000e+02 # whc
> Block FRBlock
> 1 2.000000e+01 # beta
> ## Dependent parameters, given by model restrictions.
> ## Those values should be edited following the
> ## analytical expression. MG5 ignores those values
> ## but they are important for interfacing the output of MG5
> ## to external program such as Pythia.
> DECAY 1 0.000000 # d : 0.0
> DECAY 2 0.000000 # u : 0.0
> DECAY 3 0.000000 # s : 0.0
> DECAY 4 0.000000 # c : 0.0
> DECAY 5 0.000000 # b : 0.0
> DECAY 11 0.000000 # e- : 0.0
> DECAY 12 0.000000 # ve : 0.0
> DECAY 13 0.000000 # mu- : 0.0
> DECAY 14 0.000000 # vm : 0.0
> DECAY 15 0.000000 # ta- : 0.0
> DECAY 16 0.000000 # vt : 0.0
> DECAY 21 0.000000 # g : 0.0
> DECAY 22 0.000000 # a : 0.0
> DECAY 82 0.000000 # ghg : 0.0
> DECAY 9000001 0.000000 # gha : 0.0
> DECAY 9000002 2.495200 # ghz : WZ
> DECAY 9000003 2.085000 # ghwp : WW
> DECAY 9000004 2.085000 # ghwm : WW
>
>
> ## DECAY ID WIDTH
> ## NDA ID1 ID2 ...
> DECAY -24 2.085000e+00
> 3.377e-01 2 1 -2
> 3.377e-01 2 3 -4
> 1.082e-01 2 11 -12
> 1.082e-01 2 13 -14
> 1.082e-01 2 15 -16
> DECAY 24 2.085000e+00
> 3.377e-01 2 -1 2
> 3.377e-01 2 -3 4
> 1.082e-01 2 -11 12
> 1.082e-01 2 -13 14
> 1.082e-01 2 -15 16
>
> #With this, I can have small couplings to be consistent
> # with the SM width and limit on BR (~ 0.1%), and yet generate the exotic width
> #
> DECAY -6 1.33
> 9.96e-01 2 -5 -24
> 0.10e-02 2 -4 25
> 0.10e-02 2 -2 25
> 0.05e-02 2 -4 23
> 0.05e-02 2 -2 23
> 0.05e-02 2 -4 22
> 0.05e-02 2 -2 22
> 0.05e-02 2 -5 -37
>
> DECAY 6 1.33
> 9.96e-01 2 5 24
> 0.10e-02 2 4 25
> 0.10e-02 2 2 25
> 0.05e-02 2 4 23
> 0.05e-02 2 2 23
> 0.05e-02 2 4 22
> 0.05e-02 2 2 22
> 0.05e-02 2 5 37
>
>
> ###################################
> ## INFORMATION FOR HIGGS
> ###################################
> Block Higgs
> 1 5.000000e-01 # l2
> 2 1.000000e+00 # l3
> 3 0.000000e+00 # lR7
> 5 3.000000e-01 # mixh
>
> ###################################
> ## INFORMATION FOR LOOP
> ###################################
> Block LOOP
> 1 9.118800e+01 # MU_R
>
>
> #===========================================================
> # QUANTUM NUMBERS OF NEW STATE(S) (NON SM PDG CODE)
> #===========================================================
>
> Block QNUMBERS 9000001 # gha
> 1 0 # 3 times electric charge
> 2 1 # number of spin states (2S+1)
> 3 1 # colour rep (1: singlet, 3: triplet, 8: octet)
> 4 1 # Particle/Antiparticle distinction (0=own anti)
> Block QNUMBERS 9000002 # ghz
> 1 0 # 3 times electric charge
> 2 1 # number of spin states (2S+1)
> 3 1 # colour rep (1: singlet, 3: triplet, 8: octet)
> 4 1 # Particle/Antiparticle distinction (0=own anti)
> Block QNUMBERS 9000003 # ghwp
> 1 3 # 3 times electric charge
> 2 1 # number of spin states (2S+1)
> 3 1 # colour rep (1: singlet, 3: triplet, 8: octet)
> 4 1 # Particle/Antiparticle distinction (0=own anti)
> Block QNUMBERS 9000004 # ghwm
> 1 -3 # 3 times electric charge
> 2 1 # number of spin states (2S+1)
> 3 1 # colour rep (1: singlet, 3: triplet, 8: octet)
> 4 1 # Particle/Antiparticle distinction (0=own anti)
> Block QNUMBERS 82 # ghg
> 1 0 # 3 times electric charge
> 2 1 # number of spin states (2S+1)
> 3 8 # colour rep (1: singlet, 3: triplet, 8: octet)
> 4 1 # Particle/Antiparticle distinction (0=own anti)
> Block QNUMBERS 37 # h+
> 1 3 # 3 times electric charge
> 2 1 # number of spin states (2S+1)
> 3 1 # colour rep (1: singlet, 3: triplet, 8: octet)
> 4 1 # Particle/Antiparticle distinction (0=own anti)
> Block QNUMBERS 35 # h2
> 1 0 # 3 times electric charge
> 2 1 # number of spin states (2S+1)
> 3 1 # colour rep (1: singlet, 3: triplet, 8: octet)
> 4 0 # Particle/Antiparticle distinction (0=own anti)
> Block QNUMBERS 36 # h3
> 1 0 # 3 times electric charge
> 2 1 # number of spin states (2S+1)
> 3 1 # colour rep (1: singlet, 3: triplet, 8: octet)
> 4 0 # Particle/Antiparticle distinction (0=own anti)
>
>
> My MS_debug report:
> set Nevents_for_max_weigth 100
> set max_weight_ps_point 1000
> set seed 765432
> import run.lhe
> set ms_dir MadSpin
> define l+ = e+ mu+ ta+
> define l- = e- mu- ta-
> define vl = ve vm vt
> define vl~ = ve~ vm~ vt~
> define p = g u c d s u~ c~ d~ s~
> define j = g u c d s u~ c~ d~ s~
> decay t > b h+
> decay t~ > b~ w-, w- > l- vl~
> launch
> Traceback (most recent call last):
> File "/cvmfs/atlas.cern.ch/repo/sw/software/x86_64-slc6-gcc47-opt/19.2.5/sw/lcg/external/MCGenerators_lcgcmt67c/madgraph5amc/2.6.2.atlas2/x86_64-slc6-gcc47-opt/madgraph/interface/extended_cmd.py", line 1501, in onecmd
> return self.onecmd_orig(line, **opt)
> File "/cvmfs/atlas.cern.ch/repo/sw/software/x86_64-slc6-gcc47-opt/19.2.5/sw/lcg/external/MCGenerators_lcgcmt67c/madgraph5amc/2.6.2.atlas2/x86_64-slc6-gcc47-opt/madgraph/interface/extended_cmd.py", line 1450, in onecmd_orig
> return func(arg, **opt)
> File "/cvmfs/atlas.cern.ch/repo/sw/software/x86_64-slc6-gcc47-opt/19.2.5/sw/lcg/external/MCGenerators_lcgcmt67c/madgraph5amc/2.6.2.atlas2/x86_64-slc6-gcc47-opt/madgraph/various/misc.py", line 100, in f_with_no_logger
> out = f(self, *args, **opt)
> File "/cvmfs/atlas.cern.ch/repo/sw/software/x86_64-slc6-gcc47-opt/19.2.5/sw/lcg/external/MCGenerators_lcgcmt67c/madgraph5amc/2.6.2.atlas2/x86_64-slc6-gcc47-opt/MadSpin/interface_madspin.py", line 582, in do_launch
> generate_all.run()
> File "/cvmfs/atlas.cern.ch/repo/sw/software/x86_64-slc6-gcc47-opt/19.2.5/sw/lcg/external/MCGenerators_lcgcmt67c/madgraph5amc/2.6.2.atlas2/x86_64-slc6-gcc47-opt/MadSpin/decay.py", line 2118, in run
> self.get_max_weight_from_event(decay_mapping)
> File "/cvmfs/atlas.cern.ch/repo/sw/software/x86_64-slc6-gcc47-opt/19.2.5/sw/lcg/external/MCGenerators_lcgcmt67c/madgraph5amc/2.6.2.atlas2/x86_64-slc6-gcc47-opt/MadSpin/decay.py", line 3110, in get_max_weight_from_event
> production_tag, event_map = self.load_event()
> File "/cvmfs/atlas.cern.ch/repo/sw/software/x86_64-slc6-gcc47-opt/19.2.5/sw/lcg/external/MCGenerators_lcgcmt67c/madgraph5amc/2.6.2.atlas2/x86_64-slc6-gcc47-opt/MadSpin/decay.py", line 3249, in load_event
> P_order = self.all_ME[production_tag]['tag2order'][production_tag]
> KeyError: ((-5, 21), (-6, -5, 6))
> Value of current Options:
> spinmode : madspin
> onlyhelicity : False
> seed : 765432
> max_weight_ps_point : 1000
> fixed_order : False
> nb_sigma : 0
> run_card : None
> Nevents_for_max_weigth : 100
> BW_cut : 50.0
> use_old_dir : False
> max_weight : -1
> curr_dir : MadSpin
> ms_dir : MadSpin
> max_running_process : 100
>
>
>
>
>
>
> --
> You received this question notification because you are an answer
> contact for MadGraph5_aMC@NLO.

Anna Ivina (aivina) said : #2

Hi Olivier,

Thank you for your fast reply.

I am doing it in the athena, so the release I was using was atlas related v2_6_2_atlas2 (LCG)
Now I tried to do with another version which is v2_3_3_p1
and it showed me another error

Command "launch" interrupted with error:
 KeyError : ((21, 21), (-13, -12, -5, 5, 11, 14, 21))
 Please report this bug to developers
More information is found in 'MS_debug'.
Please attach this file to your report.

Maybe the versions I am using are not the right ones?

Thanks,
anna
Anna

Can you try with 2.6.3.2 ?
MadSpin had a lot of instabilities in the last couple of version and you really need that version to be sure that MadSpin is working.

Cheers,

Olivier

> On 2 Oct 2018, at 11:32, Anna Ivina <email address hidden> wrote:
>
> Question #674585 on MadGraph5_aMC@NLO changed:
> https://answers.launchpad.net/mg5amcnlo/+question/674585
>
> Anna Ivina posted a new comment:
> Hi Olivier,
>
> Thank you for your fast reply.
>
> I am doing it in the athena, so the release I was using was atlas related v2_6_2_atlas2 (LCG)
> Now I tried to do with another version which is v2_3_3_p1
> and it showed me another error
>
> Command "launch" interrupted with error:
> KeyError : ((21, 21), (-13, -12, -5, 5, 11, 14, 21))
> Please report this bug to developers
> More information is found in 'MS_debug'.
> Please attach this file to your report.
>
> Maybe the versions I am using are not the right ones?
>
> Thanks,
> anna
> Anna
>
> --
> You received this question notification because you are an answer
> contact for MadGraph5_aMC@NLO.

Anna Ivina (aivina) said : #4

Hi Oliver,

I have tried to use the version you have told me. The error appears the same.

Before using the madspin I am using the Powheg. for pp->ttbar. And then I use the madspin for a decay.
I was told before that this error can be from the fact that I use powheg first and that when madspin tries to find all decays it also have decays with b quarks, but powheg doesn't have it. However, nobody could tell me how I could fix the madspin in this case. I tried to set the mass of b quark to zero and later in the model itsel using restrict_no-bmass, and then later put to its value in the param_card, but I do not know whether this is a good approach or not.

Do you have may be other ideas?

The error is below. Do you need may be the MS_debug as well?
Thanks you,
Anna
generate 17:29:53 INFO: Decaying the events...
generate 17:30:05 Command "launch" interrupted with error:
generate 17:30:05 KeyError : ((5, 21), (-6, 5, 6))
generate 17:30:05 Please report this bug to developers
generate 17:30:05
generate 17:30:05 More information is found in 'MS_debug'.
generate 17:30:05
generate 17:30:05 Please attach this file to your report.
generate 17:30:05 command not executed: r
generate 17:30:05 command not executed: u
generate 17:30:05 command not executed: n
generate 17:30:05 command not executed: .
generate 17:30:05 command not executed: l
generate 17:30:05 command not executed: h
generate 17:30:05 command not executed: e
generate 17:30:05 MadSpin>command not executed: r
generate 17:30:05 command not executed: u
generate 17:30:05 command not executed: n
generate 17:30:05 command not executed: .
generate 17:30:05 command not executed: l
generate 17:30:05 command not executed: h
generate 17:30:05 command not executed: e
generate 17:30:05 command not executed: r
generate 17:30:05 command not executed: u
generate 17:30:05 command not executed: n
generate 17:30:05 command not executed: .
generate 17:30:05 command not executed: l
generate 17:30:05 command not executed: h
generate 17:30:05 command not executed: e

Hi,

I have actually never use MadSpin in conjunction of POWHEG.
Even if indeed nothing prevents it (and I do not want to prevent it).

The trick to use event from other generator than MG5aMC is to have a MG5aMC banner in the top of the events file since madspin reads
1) the mg5proccard part of the header
2) the slha part of the banner

So this error indicate that your mg5proccard is not valid since you are likely to have not include some of the matrix-element that you need.
From the log, you are at least missing the following matrix-element:
5 21 > 6 -6 5 matrix element (i.e. b g > t t~ b)
So you have to add it in a way (or another) in the mg5proccard.

They are many possible syntax that you can use
in principle adding there
add process 5 21 > 6 -6 5

Cheers,

Olivier

On 3 Oct 2018, at 16:57, Anna Ivina <<email address hidden><mailto:<email address hidden>>> wrote:

Question #674585 on MadGraph5_aMC@NLO changed:
https://answers.launchpad.net/mg5amcnlo/+question/674585

Anna Ivina posted a new comment:
Hi Oliver,

I have tried to use the version you have told me. The error appears the
same.

Before using the madspin I am using the Powheg. for pp->ttbar. And then I use the madspin for a decay.
I was told before that this error can be from the fact that I use powheg first and that when madspin tries to find all decays it also have decays with b quarks, but powheg doesn't have it. However, nobody could tell me how I could fix the madspin in this case. I tried to set the mass of b quark to zero and later in the model itsel using restrict_no-bmass, and then later put to its value in the param_card, but I do not know whether this is a good approach or not.

Do you have may be other ideas?

The error is below. Do you need may be the MS_debug as well?
Thanks you,
Anna
generate 17:29:53 INFO: Decaying the events...
generate 17:30:05 Command "launch" interrupted with error:
generate 17:30:05 KeyError : ((5, 21), (-6, 5, 6))
generate 17:30:05 Please report this bug to developers
generate 17:30:05
generate 17:30:05 More information is found in 'MS_debug'.
generate 17:30:05
generate 17:30:05 Please attach this file to your report.
generate 17:30:05 command not executed: r
generate 17:30:05 command not executed: u
generate 17:30:05 command not executed: n
generate 17:30:05 command not executed: .
generate 17:30:05 command not executed: l
generate 17:30:05 command not executed: h
generate 17:30:05 command not executed: e
generate 17:30:05 MadSpin>command not executed: r
generate 17:30:05 command not executed: u
generate 17:30:05 command not executed: n
generate 17:30:05 command not executed: .
generate 17:30:05 command not executed: l
generate 17:30:05 command not executed: h
generate 17:30:05 command not executed: e
generate 17:30:05 command not executed: r
generate 17:30:05 command not executed: u
generate 17:30:05 command not executed: n
generate 17:30:05 command not executed: .
generate 17:30:05 command not executed: l
generate 17:30:05 command not executed: h
generate 17:30:05 command not executed: e

--
You received this question notification because you are an answer
contact for MadGraph5_aMC@NLO.

Anna Ivina (aivina) said : #6

Hi Olivier,

Thanks for the suggestions.
I think I had what you said
1) the mg5proccard part of the header
2) the slha part of the banner

And then I added the process as you suggested. However, the error is still there.
I just noticed one thing, that when it loads the 2HDMtypeII model it has the following:

generate 08:24:19 INFO: detected model: /cvmfs/atlas.cern.ch/repo/sw/Generators/madgraph/models/latest/2HDMtypeII. Loading...
generate 08:24:19 INFO: load particles
generate 08:24:19 INFO: load vertices
generate 08:24:19 INFO: Change particles name to pass to MG5 convention
generate 08:24:19 Defined multiparticle p = g u c d s u~ c~ d~ s~
generate 08:24:19 Defined multiparticle j = g u c d s u~ c~ d~ s~

So here I see there is no b quarks. Later on I change the definition of the p and j
define p = g u c d b s u~ c~ d~ s~ b~
define j = g u c d b s u~ c~ d~ s~ b~

and then I see the following lines:

generate 08:24:19 INFO: generating the production square matrix element
generate 08:24:19 INFO: generate p p > t t~ --no_warning=duplicate;define pert_QCD = -4 -3 -2 -1 1 2 3 4 21;add process p p > t t~ pert_QCD --no_warning=duplicate;add process b g > t t~ b;
generate 08:24:37 INFO: Done 17.32
generate 08:24:37 INFO: generating the full matrix element squared (with decay)
generate 08:24:37 INFO: generate p p > t t~, (t~ > b~ w- , w- > l- vl~ QCD=99), t > b h+ QCD=99 --no_warning=duplicate;define pert_QCD = -4 -3 -2 -1 1 2 3 4 21;add process p p > t t~ pert_QCD, (t~ > b~ w- , w- > l- vl~ QCD=99), t > b h+ QCD=99 --no_warning=duplicate;add process b g > t t~ b, (t~ > b~ w- , w- > l- vl~ QCD=99), t > b h+ QCD=99 --no_warning=duplicate;

So looks like it has 4 flavour and not 5. Maybe this is the reason why I am having the problem?
What do you think?

Thanks for helping,
Anna

Hi,

> So looks like it has 4 flavour and not 5. Maybe this is the reason why I am having the problem?

Yes that's correct, you need to tell madspin (either via the mg5proccard or via the madspin card)
to use a model which is five flavor (i.e. where the mass is hardcoded to zero).

If you need to modify the model for that you should look at the following method:
https://answers.launchpad.net/mg5amcnlo/+faq/2312

Cheers,

Olivier

> On 4 Oct 2018, at 07:32, Anna Ivina <email address hidden> wrote:
>
> Question #674585 on MadGraph5_aMC@NLO changed:
> https://answers.launchpad.net/mg5amcnlo/+question/674585
>
> Status: Answered => Open
>
> Anna Ivina is still having a problem:
> Hi Olivier,
>
> Thanks for the suggestions.
> I think I had what you said
> 1) the mg5proccard part of the header
> 2) the slha part of the banner
>
> And then I added the process as you suggested. However, the error is still there.
> I just noticed one thing, that when it loads the 2HDMtypeII model it has the following:
>
> generate 08:24:19 INFO: detected model: /cvmfs/atlas.cern.ch/repo/sw/Generators/madgraph/models/latest/2HDMtypeII. Loading...
> generate 08:24:19 INFO: load particles
> generate 08:24:19 INFO: load vertices
> generate 08:24:19 INFO: Change particles name to pass to MG5 convention
> generate 08:24:19 Defined multiparticle p = g u c d s u~ c~ d~ s~
> generate 08:24:19 Defined multiparticle j = g u c d s u~ c~ d~ s~
>
>
> So here I see there is no b quarks. Later on I change the definition of the p and j
> define p = g u c d b s u~ c~ d~ s~ b~
> define j = g u c d b s u~ c~ d~ s~ b~
>
> and then I see the following lines:
>
> generate 08:24:19 INFO: generating the production square matrix element
> generate 08:24:19 INFO: generate p p > t t~ --no_warning=duplicate;define pert_QCD = -4 -3 -2 -1 1 2 3 4 21;add process p p > t t~ pert_QCD --no_warning=duplicate;add process b g > t t~ b;
> generate 08:24:37 INFO: Done 17.32
> generate 08:24:37 INFO: generating the full matrix element squared (with decay)
> generate 08:24:37 INFO: generate p p > t t~, (t~ > b~ w- , w- > l- vl~ QCD=99), t > b h+ QCD=99 --no_warning=duplicate;define pert_QCD = -4 -3 -2 -1 1 2 3 4 21;add process p p > t t~ pert_QCD, (t~ > b~ w- , w- > l- vl~ QCD=99), t > b h+ QCD=99 --no_warning=duplicate;add process b g > t t~ b, (t~ > b~ w- , w- > l- vl~ QCD=99), t > b h+ QCD=99 --no_warning=duplicate;
>
>
> So looks like it has 4 flavour and not 5. Maybe this is the reason why I am having the problem?
> What do you think?
>
>
> Thanks for helping,
> Anna
>
> --
> You received this question notification because you are an answer
> contact for MadGraph5_aMC@NLO.

Anna Ivina (aivina) said : #8

Hi Olivier,

Thank you a lot. I saw that in 2HDMtypeII they already have the restriction with no b mass.
I have used it and looks like it processed.
I got some waring:

generate 10:18:59 INFO: Decaying the events...
generate 10:19:22 INFO: Event nb 1000 22.9s
generate 10:19:43 INFO: Event nb 2000 44s
generate 10:20:04 INFO: Event nb 3000 1m 4s
generate 10:20:26 INFO: Event nb 4000 1m 26s
generate 10:20:47 INFO: Event nb 5000 1m 47s
generate 10:21:08 INFO: Event nb 6000 2m 8s
generate 10:21:09 WARNING: Found many weight larger than the computed max_weight (12/6050 = 0.198347107438%).
generate 10:21:09
generate 10:21:09 INFO: Total number of events written: 6050/6050

Is it ok? Sorry, I just want to make sure that it is all right.

Also I wanted to ask you another question. I see that b mass is set to zero as well as the Yukawa mass of b to zero in the restriction. I have p p > t t~, (t~ > b~ w- , w- > l- vl~ ), t > b h+ process and does it mean that later in param card I need to set the Yukawa mass to appropriate value? Or they shall be left untouched?
I also want to pass events through pythia8 and I guess it will use parameters from the decay?

Thank you a lot,
Anna

Hi,

> generate 10:21:09 WARNING: Found many weight larger than the computed max_weight (12/6050 = 0.198347107438%).

This means that the max-weight was under-estimated. and that you can have a small bias due to that.
Since the bias is small, we only put a warning.
You can decide to procede (in any case you have other bias anyway) or you should ask for madspin to
increase the number of points used to compute the max_weight (via the madspin_card)

> I have p p > t t~, (t~ > b~ w- , w- > l- vl~ ), t > b h+ process and does it mean that later in param card I need to set the Yukawa mass to appropriate value?

Well what is the coupling for t > b h+ ? If it is proportional to the yukawa coupling?
You can also decide to set a restriction_card where the yukawa is not zero but where the mass is.
(But do not use feynman gauge/complex mass scheme in that case)

Cheers,

Olivier

> On 4 Oct 2018, at 09:32, Anna Ivina <email address hidden> wrote:
>
> Question #674585 on MadGraph5_aMC@NLO changed:
> https://answers.launchpad.net/mg5amcnlo/+question/674585
>
> Anna Ivina posted a new comment:
> Hi Olivier,
>
>
> Thank you a lot. I saw that in 2HDMtypeII they already have the restriction with no b mass.
> I have used it and looks like it processed.
> I got some waring:
>
> generate 10:18:59 INFO: Decaying the events...
> generate 10:19:22 INFO: Event nb 1000 22.9s
> generate 10:19:43 INFO: Event nb 2000 44s
> generate 10:20:04 INFO: Event nb 3000 1m 4s
> generate 10:20:26 INFO: Event nb 4000 1m 26s
> generate 10:20:47 INFO: Event nb 5000 1m 47s
> generate 10:21:08 INFO: Event nb 6000 2m 8s
> generate 10:21:09 WARNING: Found many weight larger than the computed max_weight (12/6050 = 0.198347107438%).
> generate 10:21:09
> generate 10:21:09 INFO: Total number of events written: 6050/6050
>
> Is it ok? Sorry, I just want to make sure that it is all right.
>
> Also I wanted to ask you another question. I see that b mass is set to zero as well as the Yukawa mass of b to zero in the restriction. I have p p > t t~, (t~ > b~ w- , w- > l- vl~ ), t > b h+ process and does it mean that later in param card I need to set the Yukawa mass to appropriate value? Or they shall be left untouched?
> I also want to pass events through pythia8 and I guess it will use parameters from the decay?
>
>
> Thank you a lot,
> Anna
>
> --
> You received this question notification because you are an answer
> contact for MadGraph5_aMC@NLO.

Anna Ivina (aivina) said : #10

Hi Olivier,

Thank you for your help

The best,
Anna

Can you help with this problem?

Provide an answer of your own, or ask Anna Ivina for more information if necessary.

To post a message you must log in.