KeyError : 'mul+' while running MadSpin in MadGraph_aMC@NLO v5.2.1.0

Bug #1304169 reported by Paul Jackson
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
MadGraph5_aMC@NLO
Invalid
Undecided
Unassigned

Bug Description

I am generating events with MadSpin set 'ON' to perform the decays and encountering an error.

I set up the following

stoppair>generate_events
The following switches determine which programs are run:
 1 Run the pythia shower/hadronization: pythia=ON
 2 Run PGS as detector simulator: pgs=ON
 3 Run Delphes as detector simulator: delphes=NOT INSTALLED
 4 Decay particles with the MadSpin module: madspin=ON
 5 Add weight to events based on coupling parameters: reweight=OFF

My madspin_card.dat looks like this:

 set max_weight_ps_point 400 # number of PS to estimate the maximum for each event
#
# specify the decay for the final state particles
decay t1 > b x1+, x1+ > w+ n1, w+ > l+ vl
decay x1+ > w+ n1
decay w+ > l+ vl
decay t1~ > b~ x1-, x1- > w- n1, w- > l- vl~
decay x1- > w- n1
decay w- > l- vl~
#
# running the actual code
launch

and I get the following output and error:

************************************************************
* *
* W E L C O M E to M A D S P I N *
* *
************************************************************
INFO: Extracting the banner ...
INFO: process: p p > t1 t1~
INFO: options:
INFO: detected model: mssm. Loading...
set max_weight_ps_point 400 # number of PS to estimate the maximum for each event
decay t1 > b x1+, x1+ > w+ n1, w+ > l+ vl
t1 > b x1+ , x1+ > n1 w+ , w+ > l+ vl
decay x1+ > w+ n1
x1+ > w+ n1
decay w+ > l+ vl
w+ > l+ vl
decay t1~ > b~ x1-, x1- > w- n1, w- > l- vl~
t1~ > b~ x1- , x1- > n1 w- , w- > l- vl~
decay x1- > w- n1
x1- > w- n1
decay w- > l- vl~
w- > l- vl~
launch
INFO: Will use seed 765275859
INFO: generating Madspin matrix element
INFO: We need to recalculate the branching fractions
INFO: using the FeynRules formula present in the model (arXiv:1402.1178)
INFO: load particles
INFO: load vertices
INFO: Restrict model mssm with file ../models/mssm/restrict_default.dat .
INFO: Run "set stdout_level DEBUG" before import for more information.
WARNING: The LO estimate for the width of particle 24
WARNING: differs from the one in the banner by 324 percent
Command "generate_events" interrupted with error:
KeyError : 'mul+'
Please report this bug on https://bugs.launchpad.net/madgraph5
More information is found in '/Users/jack/Documents/ATLAS/susy/interpret/MG5_aMC_v2_1_0/stoppair/run_07_tag_1_debug.log'.
Please attach this file to your report.

the logfile output looks like this:

generate_events
Traceback (most recent call last):
  File "/Users/jack/Documents/ATLAS/susy/interpret/MG5_aMC_v2_1_0/stoppair/bin/internal/extended_cmd.py", line 872, in onecmd
    return self.onecmd_orig(line, **opt)
  File "/Users/jack/Documents/ATLAS/susy/interpret/MG5_aMC_v2_1_0/stoppair/bin/internal/extended_cmd.py", line 865, in onecmd_orig
    return func(arg, **opt)
  File "/Users/jack/Documents/ATLAS/susy/interpret/MG5_aMC_v2_1_0/stoppair/bin/internal/madevent_interface.py", line 2126, in do_generate_events
    self.exec_cmd('decay_events -from_cards', postcmd=False)
  File "/Users/jack/Documents/ATLAS/susy/interpret/MG5_aMC_v2_1_0/stoppair/bin/internal/extended_cmd.py", line 912, in exec_cmd
    stop = Cmd.onecmd_orig(current_interface, line, **opt)
  File "/Users/jack/Documents/ATLAS/susy/interpret/MG5_aMC_v2_1_0/stoppair/bin/internal/extended_cmd.py", line 865, in onecmd_orig
    return func(arg, **opt)
  File "/Users/jack/Documents/ATLAS/susy/interpret/MG5_aMC_v2_1_0/stoppair/bin/internal/common_run_interface.py", line 1511, in do_decay_events
    madspin_cmd.import_command_file(path)
  File "/Users/jack/Documents/ATLAS/susy/interpret/MG5_aMC_v2_1_0/madgraph/interface/extended_cmd.py", line 1027, in import_command_file
    self.exec_cmd(line, precmd=True)
  File "/Users/jack/Documents/ATLAS/susy/interpret/MG5_aMC_v2_1_0/madgraph/interface/extended_cmd.py", line 912, in exec_cmd
    stop = Cmd.onecmd_orig(current_interface, line, **opt)
  File "/Users/jack/Documents/ATLAS/susy/interpret/MG5_aMC_v2_1_0/madgraph/interface/extended_cmd.py", line 865, in onecmd_orig
    return func(arg, **opt)
  File "/Users/jack/Documents/ATLAS/susy/interpret/MG5_aMC_v2_1_0/MadSpin/interface_madspin.py", line 459, in do_launch
    self.options)
  File "/Users/jack/Documents/ATLAS/susy/interpret/MG5_aMC_v2_1_0/MadSpin/decay.py", line 1966, in __init__
    self.generate_all_matrix_element()
  File "/Users/jack/Documents/ATLAS/susy/interpret/MG5_aMC_v2_1_0/madgraph/various/misc.py", line 88, in f_with_no_logger
    out = f(self, *args, **opt)
  File "/Users/jack/Documents/ATLAS/susy/interpret/MG5_aMC_v2_1_0/tests/unit_tests/various/test_aloha.py", line 50, in deco_f_set
    out = f(*args, **opt)
  File "/Users/jack/Documents/ATLAS/susy/interpret/MG5_aMC_v2_1_0/MadSpin/decay.py", line 2503, in generate_all_matrix_element
    self.get_branching_ratio()
  File "/Users/jack/Documents/ATLAS/susy/interpret/MG5_aMC_v2_1_0/MadSpin/decay.py", line 2740, in get_branching_ratio
    width.extract_br(self.list_branches, self.mgcmd)
  File "/Users/jack/Documents/ATLAS/susy/interpret/MG5_aMC_v2_1_0/MadSpin/decay.py", line 1302, in extract_br
    self.launch_width_evaluation(to_decay, mgcmd)
  File "/Users/jack/Documents/ATLAS/susy/interpret/MG5_aMC_v2_1_0/MadSpin/decay.py", line 1567, in launch_width_evaluation
    self.extract_br_from_card(pjoin(self.path_me, 'param_card.dat'))
  File "/Users/jack/Documents/ATLAS/susy/interpret/MG5_aMC_v2_1_0/MadSpin/decay.py", line 1652, in extract_br_from_card
    self.extract_br_for_antiparticle()
  File "/Users/jack/Documents/ATLAS/susy/interpret/MG5_aMC_v2_1_0/MadSpin/decay.py", line 1527, in extract_br_for_antiparticle
    self.width_value[anti_res]=self.width_value[res]
KeyError: 'mul+'

Any help on this problem and/or general guidance on setting up running with MadSpin would be appreciated.

Regards,
Paul

Revision history for this message
Olivier Mattelaer (olivier-mattelaer) wrote : Re: [Bug 1304169] [NEW] KeyError : 'mul+' while running MadSpin in MadGraph_aMC@NLO v5.2.1.0
Download full text (12.8 KiB)

Hi,

Which model did you use?

Is it the default mssm or something else?

Cheers,

Olivier
On Apr 8, 2014, at 5:48 AM, Paul Jackson <email address hidden> wrote:

> Public bug reported:
>
> I am generating events with MadSpin set 'ON' to perform the decays and
> encountering an error.
>
> I set up the following
>
> stoppair>generate_events
> The following switches determine which programs are run:
> 1 Run the pythia shower/hadronization: pythia=ON
> 2 Run PGS as detector simulator: pgs=ON
> 3 Run Delphes as detector simulator: delphes=NOT INSTALLED
> 4 Decay particles with the MadSpin module: madspin=ON
> 5 Add weight to events based on coupling parameters: reweight=OFF
>
>
> My madspin_card.dat looks like this:
>
> set max_weight_ps_point 400 # number of PS to estimate the maximum for each event
> #
> # specify the decay for the final state particles
> decay t1 > b x1+, x1+ > w+ n1, w+ > l+ vl
> decay x1+ > w+ n1
> decay w+ > l+ vl
> decay t1~ > b~ x1-, x1- > w- n1, w- > l- vl~
> decay x1- > w- n1
> decay w- > l- vl~
> #
> # running the actual code
> launch
>
>
> and I get the following output and error:
>
>
> ************************************************************
> * *
> * W E L C O M E to M A D S P I N *
> * *
> ************************************************************
> INFO: Extracting the banner ...
> INFO: process: p p > t1 t1~
> INFO: options:
> INFO: detected model: mssm. Loading...
> set max_weight_ps_point 400 # number of PS to estimate the maximum for each event
> decay t1 > b x1+, x1+ > w+ n1, w+ > l+ vl
> t1 > b x1+ , x1+ > n1 w+ , w+ > l+ vl
> decay x1+ > w+ n1
> x1+ > w+ n1
> decay w+ > l+ vl
> w+ > l+ vl
> decay t1~ > b~ x1-, x1- > w- n1, w- > l- vl~
> t1~ > b~ x1- , x1- > n1 w- , w- > l- vl~
> decay x1- > w- n1
> x1- > w- n1
> decay w- > l- vl~
> w- > l- vl~
> launch
> INFO: Will use seed 765275859
> INFO: generating Madspin matrix element
> INFO: We need to recalculate the branching fractions
> INFO: using the FeynRules formula present in the model (arXiv:1402.1178)
> INFO: load particles
> INFO: load vertices
> INFO: Restrict model mssm with file ../models/mssm/restrict_default.dat .
> INFO: Run "set stdout_level DEBUG" before import for more information.
> WARNING: The LO estimate for the width of particle 24
> WARNING: differs from the one in the banner by 324 percent
> Command "generate_events" interrupted with error:
> KeyError : 'mul+'
> Please report this bug on https://bugs.launchpad.net/madgraph5
> More information is found in '/Users/jack/Documents/ATLAS/susy/interpret/MG5_aMC_v2_1_0/stoppair/run_07_tag_1_debug.log'.
> Please attach this file to your report.
>
>
> the logfile output looks like this:
>
> generate_events
> Traceback (most recent call last):
> File "/Users/jack/Documents/ATLAS/susy/interpret/MG5_aMC_v2_1_0/stoppair/bin/internal/extended_cmd.py", line 872, in onecmd
> return self.onecmd_orig(line, **opt)
> File "/Users/jack/Documen...

Revision history for this message
Paul Jackson (p-jackson-9) wrote :

Hi Olivier,

Yes it was the default mssm (using the standard 'import model mssm' style command).
There would not be such a comment running with MadSpin turned off and I see 'mul+' defined in the model.

Thanks for the quick response.

Paul

Revision history for this message
Olivier Mattelaer (olivier-mattelaer) wrote : Re: [Bug 1304169] KeyError : 'mul+' while running MadSpin in MadGraph_aMC@NLO v5.2.1.0
Download full text (7.8 KiB)

Dear Paul,

Sorry for the delay,

First your decay syntax does not seems valid:
it should be
> decay t1 > b x1+, (x1+ > w+ n1, w+ > l+ vl)
> decay x1+ > w+ n1
> decay w+ > l+ vl
> decay t1~ > b~ x1-,( x1- > w- n1, w- > l- vl~ )
> decay x1- > w- n1
> decay w- > l- vl~

The parenthesis are required for sub-decay.

This actually does not seems enough to make it work but at least this fix the problem that you report.
(at least it goes further that the point that you report in 2.1.1) The problem remaining is actually a typical MSSM problem
(Conversion between SLHA1 and SLHA2 format).

If you don’t plan to use pythia6 for the shower, then the best is to copy the model under a new name.
This then bypass the conversion to SLHA1 which is required for pythia.

I will try to understand why the conversion creates problem here.

Cheers,

Olivier

On Apr 8, 2014, at 11:07 PM, Paul Jackson <email address hidden> wrote:

> Hi Olivier,
>
>
> Yes it was the default mssm (using the standard 'import model mssm' style command).
> There would not be such a comment running with MadSpin turned off and I see 'mul+' defined in the model.
>
> Thanks for the quick response.
>
> Paul
>
> --
> You received this bug notification because you are subscribed to
> MadGraph5_aMC@NLO.
> https://bugs.launchpad.net/bugs/1304169
>
> Title:
> KeyError : 'mul+' while running MadSpin in MadGraph_aMC@NLO v5.2.1.0
>
> Status in MadGraph5_aMC@NLO Generator:
> New
>
> Bug description:
> I am generating events with MadSpin set 'ON' to perform the decays and
> encountering an error.
>
> I set up the following
>
> stoppair>generate_events
> The following switches determine which programs are run:
> 1 Run the pythia shower/hadronization: pythia=ON
> 2 Run PGS as detector simulator: pgs=ON
> 3 Run Delphes as detector simulator: delphes=NOT INSTALLED
> 4 Decay particles with the MadSpin module: madspin=ON
> 5 Add weight to events based on coupling parameters: reweight=OFF
>
>
> My madspin_card.dat looks like this:
>
> set max_weight_ps_point 400 # number of PS to estimate the maximum for each event
> #
> # specify the decay for the final state particles
> decay t1 > b x1+, x1+ > w+ n1, w+ > l+ vl
> decay x1+ > w+ n1
> decay w+ > l+ vl
> decay t1~ > b~ x1-, x1- > w- n1, w- > l- vl~
> decay x1- > w- n1
> decay w- > l- vl~
> #
> # running the actual code
> launch
>
>
>
> and I get the following output and error:
>
>
> ************************************************************
> * *
> * W E L C O M E to M A D S P I N *
> * *
> ************************************************************
> INFO: Extracting the banner ...
> INFO: process: p p > t1 t1~
> INFO: options:
> INFO: detected model: mssm. Loading...
> set max_weight_ps_point 400 # number of PS to estimate the maximum for each event
> decay t1 > b x1+, x1+ > w+ n1, w+ > l+ vl
> t1 > b x1+ , x1+ > n1 w+ , w+ > l+ vl
> decay x1+ > w+ n1
> ...

Read more...

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

Dear Paul,

Actually the second problem seems linked to the mass-spectrum that I use.
So simply the change of syntax for the decay might be enough to fix your problem.

Cheers,

Olivier

On Apr 15, 2014, at 8:03 PM, Olivier Mattelaer <email address hidden> wrote:

> Dear Paul,
>
> Sorry for the delay,
>
> First your decay syntax does not seems valid:
> it should be
>> decay t1 > b x1+, (x1+ > w+ n1, w+ > l+ vl)
>> decay x1+ > w+ n1
>> decay w+ > l+ vl
>> decay t1~ > b~ x1-,( x1- > w- n1, w- > l- vl~ )
>> decay x1- > w- n1
>> decay w- > l- vl~
>
> The parenthesis are required for sub-decay.
>
> This actually does not seems enough to make it work but at least this fix the problem that you report.
> (at least it goes further that the point that you report in 2.1.1) The problem remaining is actually a typical MSSM problem
> (Conversion between SLHA1 and SLHA2 format).
>
> If you don’t plan to use pythia6 for the shower, then the best is to copy the model under a new name.
> This then bypass the conversion to SLHA1 which is required for pythia.
>
> I will try to understand why the conversion creates problem here.
>
> Cheers,
>
> Olivier
>
>
> On Apr 8, 2014, at 11:07 PM, Paul Jackson <email address hidden>
> wrote:
>
>> Hi Olivier,
>>
>>
>> Yes it was the default mssm (using the standard 'import model mssm' style command).
>> There would not be such a comment running with MadSpin turned off and I see 'mul+' defined in the model.
>>
>> Thanks for the quick response.
>>
>> Paul
>>
>> --
>> You received this bug notification because you are subscribed to
>> MadGraph5_aMC@NLO.
>> https://bugs.launchpad.net/bugs/1304169
>>
>> Title:
>> KeyError : 'mul+' while running MadSpin in MadGraph_aMC@NLO v5.2.1.0
>>
>> Status in MadGraph5_aMC@NLO Generator:
>> New
>>
>> Bug description:
>> I am generating events with MadSpin set 'ON' to perform the decays and
>> encountering an error.
>>
>> I set up the following
>>
>> stoppair>generate_events
>> The following switches determine which programs are run:
>> 1 Run the pythia shower/hadronization: pythia=ON
>> 2 Run PGS as detector simulator: pgs=ON
>> 3 Run Delphes as detector simulator: delphes=NOT INSTALLED
>> 4 Decay particles with the MadSpin module: madspin=ON
>> 5 Add weight to events based on coupling parameters: reweight=OFF
>>
>>
>> My madspin_card.dat looks like this:
>>
>> set max_weight_ps_point 400 # number of PS to estimate the maximum for each event
>> #
>> # specify the decay for the final state particles
>> decay t1 > b x1+, x1+ > w+ n1, w+ > l+ vl
>> decay x1+ > w+ n1
>> decay w+ > l+ vl
>> decay t1~ > b~ x1-, x1- > w- n1, w- > l- vl~
>> decay x1- > w- n1
>> decay w- > l- vl~
>> #
>> # running the actual code
>> launch
>>
>>
>>
>> and I get the following output and error:
>>
>>
>> ************************************************************
>> * *
>> * W E L C O M E to M A D S P I N *
>> * *
>> *********************************...

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

Other bug subscribers

Remote bug watches

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