NMSSM Higgs problem with Event Generation
Hello,
I have been using Madgraph 5 to attempt to produce this process in the NMSSM model:
p p > w+ h01, \ (w+ > e+ ve , h01 > a01 a01 , a01 > mu+ mu-, a01 > mu+ mu-)
Each one of the particles is defined in the model already and all but the last two decays are already defined vertecies. I defined the a01 to the muon pair vertex. The problem arises when I launch the file after I generate the process and output it to the file. It should generate 10,000 events, but after 30 minutes or so, it only generates 19. Pasted below is the log of a shorter run where I requested only 20 events. This took only about 5-10 minutes to produce.
*******
* *
* W E L C O M E to M A D G R A P H 5 *
* *
* *
* * * *
* * * * * *
* * * * * 5 * * * * *
* * * * * *
* * * *
* *
* VERSION 1.3.24 2011-10-22 *
* *
* The MadGraph Development Team - Please visit us at *
* https:/
* *
* Type 'help' for in-line help. *
* Type 'tutorial' to learn how MG5 works *
* *
*******
load MG5 configuration from ../input/
Using default text editor "vi". Set another one in ./input/
Using default eps viewer "gv". Set another one in ./input/
Using default web browser "firefox". Set another one in ./input/
Loading default model: sm
models.import_ufo: Restrict model sm with file ../models/
models.import_ufo: 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~
mg5>launch higgs_h01_
WARNING: If you edit this file don't forget to modify
the width of all particles.
Do you want to edit file: param_card.dat? [y, n, path of the new param_card.dat]
n
Do you want to edit file: run_card.dat? [y, n, path of the new run_card.dat]
y
Fri Mar 16 16:00:39 PDT 2012
Generating 20 events
Cleaning directories
Cleaning SubProcesses.
Compiling Source
Starting jobs
Compiling libraries
Working on subprocess:
P0_
real 0m1.910s
user 0m1.818s
sys 0m0.070s
real 0m1.943s
user 0m1.821s
sys 0m0.096s
0_qq_wph01_wp_lvl 0.18482E+05
1 553010.00000000000 0.0000000000000000
Results 18482.000000000000 553010.00000000000 169 215109878.87133428
1 1 18482.000000000000 0
Updated results in file results.html
Compiling libraries
Using random number seed offset = 24
P0_qq_wph01_wp_lvl
Launching job ajob1
real 2m9.714s
user 2m8.999s
sys 0m0.198s
0_qq_wph01_wp_lvl 0.22756E+10
1 34077000000.000000 0.0000000000000000
Results 2275600000.0000000 34077000000.000000 81 4592712849797.8555
1 1 2275600000.0000000 0
Updated results in file results.html
0_qq_wph01_wp_lvl 0.22756E+10
1 34077000000.000000 0.0000000000000000
Results 2275600000.0000000 34077000000.000000 81 4592712849797.8555
1 1 2275600000.0000000 0
Updated results in file results.html
Compiling libraries
Using random number seed offset = 24
P0_qq_wph01_wp_lvl
Launching job ajob1
real 2m9.670s
user 2m9.428s
sys 0m0.134s
0_qq_wph01_wp_lvl 0.36531E+09
1 0.0000000000000000 9919200000.0000000
Results 365310000.00000000 9919200000.0000000 839 786.49518224127019
1 1 365310000.00000000 0
Updated results in file results.html
0_qq_wph01_wp_lvl 0.36531E+09
1 0.0000000000000000 9919200000.0000000
Results 365310000.00000000 9919200000.0000000 839 786.49518224127019
1 1 365310000.00000000 0
Updated results in file results.html
Combining Events
Warning: parameter xmtcentral not found
setting it to default value 0.0000000000000000
Warning: parameter d not found
setting it to default value 1.0000000000000000
Warning: parameter fixed_couplings not found
setting it to default value T
Warning: parameter lhaid not found
setting it to default value 10042
A PDF is used, so alpha_s(MZ) is going to be modified
Old value of alpha_s from param_card: 0.11719999999999997
New value of alpha_s from PDF cteq6l1: 0.13000000000000000
Results.dat xsec = 365310000.00000000
Found 1 subprocesses
SubProcess/Channel kept read xsec
P0_qq_wph01_
Iteration 1 too large truncation 0.95145630933121728 1
Iteration 2 too large truncation 0.93689320213058247 1
Iteration 3 too large truncation 0.91796116276975737 1
Iteration 4 too large truncation 0.89334951160068443 1
Iteration 5 too large truncation 0.86135436508088992 1
Iteration 6 too large truncation 0.81976067460515678 1
Iteration 7 too large truncation 0.76568887698670374 1
Iteration 8 too large truncation 0.69539554008271498 1
Iteration 9 too large truncation 0.60401420210752954 1
Iteration 10 too large truncation 0.48521846273978825 1
Iteration 11 too large truncation 0.33078400156172466 1
Iteration 12 too large truncation 0.13001920203024200 1
Iteration 13 too few events 0.0000000000000000 1
Iteration 14 too few events 0.0000000000000000 1
Iteration 15 too few events 0.0000000000000000 1
Iteration 16 too large truncation 3.0330277342882
Iteration 17 too few events 0.0000000000000000 0
Iteration 18 too few events 0.0000000000000000 1
Iteration 19 too few events 0.0000000000000000 1
Iteration 20 too few events 0.0000000000000000 1
Unable to get 20 events. Writing 1
Unweighting selected 1 events.
Truncated 0.00% of cross section
putting the banner
Storing files
P0_qq_wph01_wp_lvl
Storing Events
Storing files
P0_qq_wph01_wp_lvl
Fri Mar 16 16:05:02 PDT 2012
The width is 0.36531E+09 +- 0.00000E+00 GeV
more information in higgs_h01_
It only writes 1 event after asking for 20. From here, I attempted to produce interactions of each individual parts:
p p > w+ h01
w+ > e+ ve
h01 > a01 a01
a01 > mu+ mu-
And each of them produce events on their own. Once put together, something goes wrong. I'm stuck on this. If you have any ideas or questions, don't hesitate to ask.
One last note, the one event generated cuts out everything after w+ > e+ ve doesn't register. The diagram stops after that.
Any help will be much appreciated. Thank you.
-Kyle
Question information
- Language:
- English Edit question
- Status:
- Answered
- Assignee:
- No assignee Edit question
- Last query:
- Last reply:
Can you help with this problem?
Provide an answer of your own, or ask kyle for more information if necessary.