Unable to generate Yoda
I'm running the process g g > h > h h in smeft.
I changed rivet card set run_rivet_later False.
INFO: running rivet
INFO: Running Rivet with /home/parallels
INFO: rivet done
INFO: storing files of previous run
INFO: Storing Pythia8 files of previous run
INFO: Done
INFO: running rivet
INFO: rivet done
quit
INFO:
more information in /home/parallels
but I couldn't found yoda file after running this process.
Question information
- Language:
- English Edit question
- Status:
- Answered
- Assignee:
- Sihyun Jeon Edit question
- Last query:
- Last reply:
Revision history for this message
|
#1 |
Hi can you post here the txt file in /home/parallels
Revision history for this message
|
#2 |
This is content of that file:
<LesHouchesEvents version="3.0">
<header>
<!--
#******
# *
# MadGraph5_aMC@NLO *
# *
# Going Beyond *
# *
# http://
# http://
# http://
# *
# The MadGraph5_aMC@NLO team *
# *
#......
# *
# This file contains all the information necessary to reproduce *
# the events generated: *
# *
# 1. software version *
# 2. proc_card : code generation info including model *
# 3. param_card : model primary parameters in the LH format *
# 4. run_card : running parameters (collider and cuts) *
# 5. pythia_card : present only if pythia has been run *
# 6. pgs_card : present only if pgs has been run *
# 7. delphes_cards : present only if delphes has been run *
# *
# *
#******
-->
<MGVersion>
3.4.0.RC2
</MGVersion>
<MG5ProcCard>
<![CDATA[
#******
#* MadGraph5_aMC@NLO *
#* *
#* * * *
#* * * * * *
#* * * * * 5 * * * * *
#* * * * * *
#* * * *
#* *
#* *
#* VERSION 3.4.0.RC2 2022-04-16 *
#* *
#* The MadGraph5_aMC@NLO Development Team - Find us at *
#* https:/
#* *
#******
#* *
#* Command File for MadGraph5_aMC@NLO *
#* *
#* run as ./bin/mg5_aMC filename *
#* *
#******
set group_subprocesses Auto
set ignore_
set low_mem_
set complex_mass_scheme False
set include_
set gauge unitary
set loop_optimized_
set loop_color_flows False
set max_npoint_
set default_
set max_t_for_channel 99
set zerowidth_tchannel True
set nlo_mixed_expansion True
import model sm
define p = g u c d s u~ c~ d~ s~
define j = g u c d s u~ c~ d~ s~
define l+ = e+ mu+
define l- = e- mu-
define vl = ve vm vt
define vl~ = ve~ vm~ vt~
import model SMEFTatNLO-NLO
define p = 21 2 4 1 3 -2 -4 -1 -3 5 -5 # pass to 5 flavors
define j = p
generate g g > h > h h aS==2 aEW==2 NP=2 [QCD]
output hhh_2NP1QED_SMEFT
]]>
</MG5ProcCard>
<MGProcCard>
#******
# MadGraph/MadEvent *
# http://
# *
# proc_card.dat *
#******
# *
# This Files is generated by MADGRAPH 5 *
# *
# WARNING: This Files is generated for MADEVENT (compatibility issue)*
# This files is NOT a valid MG4 proc_card.dat *
# Running this in MG4 will NEVER reproduce the result of MG5*
# *
#******
#******
# Process(es) requested : mg2 input *
#******
# Begin PROCESS # This is TAG. Do not modify this line
g g > h > h h [QCD] #Process
# Be carefull the coupling are here in MG5 convention
aS==2
aEW==2
NP=2
end_coup # End the couplings input
done # this tells MG there are no more procs
# End PROCESS # This is TAG. Do not modify this line
#******
# Model information *
#******
# Begin MODEL # This is TAG. Do not modify this line
SMEFTatNLO-NLO
# End MODEL # This is TAG. Do not modify this line
#******
# Start multiparticle definitions *
#******
# Begin MULTIPARTICLES # This is TAG. Do not modify this line
# End MULTIPARTICLES # This is TAG. Do not modify this line
</MGProcCard>
<MGRunCard>
<![CDATA[
#******
# MadGraph5_aMC@NLO *
# *
# run_card.dat MadEvent *
# *
# This file is used to set the parameters of the run. *
# *
# Some notation/
# *
# Lines starting with a '# ' are info or comments *
# *
# mind the format: value = variable ! comment *
# *
# To display more options, you can type the command: *
# update to_full *
#******
#
#******
# Tag name for the run (one word) *
#******
tag_1 = run_tag ! name of the run
#******
# Number of events and rnd seed *
# Warning: Do not generate more than 1M events in a single run *
#******
10000 = nevents ! Number of unweighted events requested
21 = iseed ! rnd seed (0=assigned automatically=
#******
# Collider type and energy *
# lpp: 0=No PDF, 1=proton, -1=antiproton, 2=elastic photon of proton,*
# +/-3=PDF of electron/positron beam *
# +/-4=PDF of muon/antimuon beam *
#******
1 = lpp1 ! beam 1 type
1 = lpp2 ! beam 2 type
6500.0 = ebeam1 ! beam 1 total energy in GeV
6500.0 = ebeam2 ! beam 2 total energy in GeV
# To see polarised beam options: type "update beam_pol"
#******
# PDF CHOICE: this automatically fixes alpha_s and its evol. *
# pdlabel: lhapdf=LHAPDF (installation needed) [1412.7420] *
# iww=Improved Weizsaecker-
# eva=Effective W/Z/A Approx. [21yy.zzzzz] *
# none=No PDF, same as lhapdf with lppx=0 *
#******
nn23lo1 = pdlabel ! PDF set
230000 = lhaid ! if pdlabel=lhapdf, this is the lhapdf number
# To see heavy ion options: type "update ion_pdf"
#******
# Renormalization and factorization scales *
#******
False = fixed_ren_scale ! if .true. use fixed ren scale
False = fixed_fac_scale ! if .true. use fixed fac scale
91.188 = scale ! fixed ren scale
91.188 = dsqrt_q2fact1 ! fixed fact scale for pdf1
91.188 = dsqrt_q2fact2 ! fixed fact scale for pdf2
3 = dynamical_
1.0 = scalefact ! scale factor for event-by-event scales
#******
# Type and output format
#******
False = gridpack !True = setting up the grid pack
-1.0 = time_of_flight ! threshold (in mm) below which the invariant livetime is not written (-1 means not written)
average = event_norm ! average/sum. Normalization of the weight in the LHEF
# To see MLM/CKKW merging options: type "update MLM" or "update CKKW"
#******
#
#******
# Phase-Space Optimization strategy (basic options)
#******
1 = nhel ! using helicities importance sampling or not.
2 = sde_strategy ! default integration strategy (hep-ph/2021.00773)
! 2 is new strategy (using only the denominator)
# To see advanced option for Phase-Space optimization: type "update psoptim"
#******
# Generation bias, check the wiki page below for more information: *
# 'cp3.irmp.
#******
None = bias_module ! Bias type of bias, [None, ptj_bias, -custom_folder-]
{} = bias_parameters ! Specifies the parameters of the module.
#
#******
# Parton level cuts definition *
#******
0.0 = dsqrt_shat ! minimal shat for full process
#
#
#******
# BW cutoff (M+/-bwcutoff*
#******
15.0 = bwcutoff ! (M+/-bwcutoff*
#******
# Standard Cuts *
#******
# Minimum and maximum pt's (for max, -1 means no cut) *
#******
{} = pt_min_pdg ! pt cut for other particles (use pdg code). Applied on particle and anti-particle
{} = pt_max_pdg ! pt cut for other particles (syntax e.g. {6: 100, 25: 50})
#
# For display option for energy cut in the partonic center of mass frame type 'update ecut'
#
#******
# Maximum and minimum absolute rapidity (for max, -1 means no cut) *
#******
{} = eta_min_pdg ! rap cut for other particles (use pdg code). Applied on particle and anti-particle
{} = eta_max_pdg ! rap cut for other particles (syntax e.g. {6: 2.5, 23: 5})
#******
# Minimum and maximum DeltaR distance *
#******
#******
# Minimum and maximum invariant mass for pairs *
#******
{} = mxx_min_pdg ! min invariant mass of a pair of particles X/X~ (e.g. {6:250})
{'default': False} = mxx_only_
#******
# Inclusive cuts *
#******
0.0 = ptheavy ! minimum pt for at least one heavy final state
#******
# maximal pdg code for quark to be considered as a light jet *
# (otherwise b cuts are applied) *
#******
4 = maxjetflavor ! Maximum jet pdg code
#******
#
#******
# Store info for systematics studies *
# WARNING: Do not use for interference type of computation *
#******
False = use_syst ! Enable systematics studies
#
none = systematics_program ! none, systematics [python], SysCalc [depreceted, C++]
['--mur=0.5,1,2', '--muf=0.5,1,2', '--pdf=errorset'] = systematics_
]]>
</MGRunCard>
<slha>
#######
## PARAM_CARD AUTOMATICALY GENERATED BY MG5 FOLLOWING UFO MODEL ####
#######
## ##
## Width set on Auto will be computed following the information ##
## present in the decay.py files of the model. ##
## See arXiv:1402.1178 for more details. ##
## ##
#######
#######
## INFORMATION FOR DIM6
#######
Block dim6
1 1.000000e+03 # Lambda
2 6.108140e-01 # cpDC
3 9.957510e-01 # cpWB
4 8.182060e-01 # cdp
5 7.653970e-01 # cp
6 1.312900e-02 # cWWW
9 6.693150e-01 # cpW
10 7.688960e-01 # cpBB
#######
## INFORMATION FOR DIM62F
#######
Block dim62f
1 3.098950e-01 # cpl1
2 3.091480e-01 # cpl2
3 6.648000e-03 # cpl3
4 9.632220e-01 # c3pl1
5 1.338020e-01 # c3pl2
6 4.725400e-02 # c3pl3
7 7.630370e-01 # cpe
8 4.944650e-01 # cpmu
9 8.460010e-01 # cpta
10 9.954370e-01 # cpqMi
11 9.196930e-01 # cpq3i
12 1.789460e-01 # cpQ3
13 8.670580e-01 # cpQM
14 9.301320e-01 # cpu
15 3.436890e-01 # cpt
16 6.144110e-01 # cpd
19 4.227280e-01 # ctp
22 4.997300e-02 # ctZ
23 7.619010e-01 # ctW
24 8.664520e-01 # ctG
#######
## INFORMATION FOR DIM64F
#######
Block dim64f
1 1.940700e-02 # cQq83
2 6.863600e-02 # cQq81
3 8.323820e-01 # cQu8
4 4.331910e-01 # ctq8
6 6.320110e-01 # cQd8
7 2.989460e-01 # ctu8
8 1.982190e-01 # ctd8
10 2.253190e-01 # cQq13
11 4.897740e-01 # cQq11
12 1.497200e-02 # cQu1
13 1.968860e-01 # ctq1
14 2.762590e-01 # cQd1
16 9.010070e-01 # ctu1
17 1.554570e-01 # ctd1
19 6.718310e-01 # cQQ8
20 7.328400e-02 # cQQ1
21 3.353720e-01 # cQt1
23 4.819290e-01 # ctt1
25 7.021570e-01 # cQt8
#######
## INFORMATION FOR DIM64F2L
#######
Block dim64f2l
1 9.649570e-01 # cQlM1
2 6.325050e-01 # cQlM2
3 4.239140e-01 # cQl31
4 4.476180e-01 # cQl32
5 7.508830e-01 # cQe1
6 4.365400e-01 # cQe2
7 9.460650e-01 # ctl1
8 4.814300e-01 # ctl2
9 9.203170e-01 # cte1
10 5.439660e-01 # cte2
13 4.391250e-01 # cQlM3
14 9.830880e-01 # cQl33
15 3.286980e-01 # cQe3
16 3.820540e-01 # ctl3
17 4.512770e-01 # cte3
#######
## INFORMATION FOR DIM64F4L
#######
Block dim64f4l
1 3.452570e-01 # cll1111
2 9.164160e-01 # cll2222
3 1.702430e-01 # cll3333
4 7.336150e-01 # cll1122
5 6.389080e-01 # cll1133
6 2.988000e-02 # cll2233
7 8.175110e-01 # cll1221
8 4.707800e-02 # cll1331
9 5.279080e-01 # cll2332
#######
## INFORMATION FOR MASS
#######
Block mass
6 1.720000e+02 # MT
23 9.118760e+01 # MZ
24 7.982440e+01 # MW
25 1.250000e+02 # MH
## 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.000000e+00 # d : 0.0
2 0.000000e+00 # u : 0.0
3 0.000000e+00 # s : 0.0
4 0.000000e+00 # c : 0.0
5 0.000000e+00 # b : 0.0
11 0.000000e+00 # e- : 0.0
12 0.000000e+00 # ve : 0.0
13 0.000000e+00 # mu- : 0.0
14 0.000000e+00 # vm : 0.0
15 0.000000e+00 # ta- : 0.0
16 0.000000e+00 # vt : 0.0
21 0.000000e+00 # g : 0.0
22 0.000000e+00 # a : 0.0
9000002 9.118760e+01 # ghz : MZ
9000003 7.982440e+01 # ghwp : MW
9000004 7.982440e+01 # ghwm : MW
#######
## INFORMATION FOR RENOR
#######
Block renor
1 9.118000e+01 # mueft
#######
## INFORMATION FOR SMINPUTS
#######
Block sminputs
2 1.166370e-05 # Gf
3 1.184000e-01 # aS (Note that Parameter not used if you use a PDF set)
#######
## INFORMATION FOR YUKAWA
#######
Block yukawa
6 1.720000e+02 # ymt
#######
## INFORMATION FOR DECAY
#######
DECAY 6 1.470800e+00 # WT
DECAY 23 2.416023e+00 # WZ
DECAY 24 2.002950e+00 # WW
DECAY 25 4.088000e-03 # WH
## 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.000000e+00 # d : 0.0
DECAY 2 0.000000e+00 # u : 0.0
DECAY 3 0.000000e+00 # s : 0.0
DECAY 4 0.000000e+00 # c : 0.0
DECAY 5 0.000000e+00 # b : 0.0
DECAY 11 0.000000e+00 # e- : 0.0
DECAY 12 0.000000e+00 # ve : 0.0
DECAY 13 0.000000e+00 # mu- : 0.0
DECAY 14 0.000000e+00 # vm : 0.0
DECAY 15 0.000000e+00 # ta- : 0.0
DECAY 16 0.000000e+00 # vt : 0.0
DECAY 21 0.000000e+00 # g : 0.0
DECAY 22 0.000000e+00 # a : 0.0
DECAY 9000002 2.416023e+00 # ghz : WZ
DECAY 9000003 2.002950e+00 # ghwp : WW
DECAY 9000004 2.002950e+00 # ghwm : WW
#======
# 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/
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/
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/
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/
Block QNUMBERS 9000005 # 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/
</slha>
<MGPythiaCard>
<![CDATA[
!
! It is possible to run this card manually with:
! LD_LIBRARY_
!
!
! Pythia8 cmd card automatically generated by MadGraph5_aMC@NLO
! For more information on the use of the MG5aMC / Pythia8 interface, visit
! https:/
!
! ==================
! General parameters
! ==================
!
Main:numberOfEvents = -1
!
! -------
! Specify the HEPMC output of the Pythia8 shower. You can set it to:
! hepmc : MG5aMC will automatically place it the run_<i> directory
! hepmc.gz : Same as 'hepmc', but also will compress the output file.
! hepmcremove : MG5aMC will automatically remove the file at the end of the run.
! (usefull when running with Delphes)
! hepmc@<hepmc_path> :
! User defined path where the HEPMC file must written. It will
! therefore not be placed in the run_<i> directory. The
! specified path, if not absolute, will be relative to
! the Event/run_<i> directory of the process output.
! /dev/null : to turn off the HEPMC output.
! fifo : to have MG5aMC setup the piping of the PY8 output to
! analysis tools such as MadAnalysis5.
! fifo@<fifo_path> :
! Same as 'fifo', but selecting a custom path to create the
! fifo pipe. (useful to select a mounted drive that supports
! fifo). Note that the fifo file extension *must* be '.hepmc.fifo'.
! -------
!
HEPMCoutput:file = tag_1_pythia8_
!
! -------
! Parameters relevant only when performing MLM merging, which can be
! turned on by setting ickkw to '1' in the run_card and chosing a
! positive value for the parameter xqcut.
! For details, see section 'Jet Matching' on the left-hand menu of
! http://
! -------
! If equal to -1.0, MadGraph5_aMC@NLO will set it automatically based
! on the parameter 'xqcut' of the run_card.dat
! The following parameter was forced to be commented out by MG5aMC.
! JetMatching:qCut = -1.0
! Use default kt-MLM to match parton level jets to those produced by the
! shower. But the other Shower-kt scheme is available too with this option.
! The following parameter was forced to be commented out by MG5aMC.
! JetMatching:
! A value of -1 means that it is automatically guessed by MadGraph.
! It is however always safer to explicitly set it.
! The following parameter was forced to be commented out by MG5aMC.
! JetMatching:nJetMax = -1
!
! -------
! Parameters relevant only when performing CKKW-L merging, which can
! be turned on by setting the parameter 'ptlund' *or* 'ktdurham' to
! a positive value.
! For details, see section 'CKKW-L Merging' on the left-hand menu of
! http://
! -------
! Central merging scale values you want to be used.
! If equal to -1.0, then MadGraph5_aMC@NLO will set this automatically
! based on the parameter 'ktdurham' of the run_card.dat
! The following parameter was forced to be commented out by MG5aMC.
! Merging:TMS = -1.0
! This must be set manually, according to Pythia8 directives.
! An example of possible value is 'pp>LEPTONS,
! Alternatively, from Pythia v8.223 onwards, the value 'guess' can be
! used to instruct Pythia to guess the hard process. The guess would mean
! that all particles apart from light partons will be considered as a part
! of the hard process. This guess is prone to errors if the desired hard
! process is complicated (i.e. contains light partons). The user should
! then be wary of suspicious error messages in the Pythia log file.
! The following parameter was forced to be commented out by MG5aMC.
! Merging:Process = <set_by_user>
! A value of -1 means that it is automatically guessed by MadGraph.
! It is however always safer to explicitly set it.
! The following parameter was forced to be commented out by MG5aMC.
! Merging:nJetMax = -1
!
! For all merging schemes, decide whehter you want the merging scale
! variation computed for only the central weights or all other
! PDF and scale variation weights as well
SysCalc:
!
! =======
! User customized parameters
! =======
!
! By default, Pythia8 generates multi-parton interaction events. This is
! often irrelevant for phenomenology and very slow. You can turn this
! feature off by uncommenting the line below if so desired.
!partonlevel:mpi = off
!
! Additional technical parameters set by MG5_aMC.
!
! Tell Pythia8 that an LHEF input is used.
Beams:frameType=4
! 1.0 corresponds to HEPMC weight given in [mb]. We choose here the [pb] normalization.
HEPMCoutput:
! Be more forgiving with momentum mismatches.
Check:epTolErr=
JetMatching:
! Specify one must read inputs from the MadGraph banner.
JetMatching:
!
! =======
! Subrun definitions
! =======
!
LHEFInputs:
Main:subrun=0
!
! Defi
</LesHouchesEvents>
Revision history for this message
|
#3 |
Hmmmm this is weird because we did several unit tests - but maybe this was one of the corner case we couldn't think of.
I have to figure out what the issue is but for now, if you go to [1], you would probably see run_rivet.sh file. If you execute that I think you would get the yoda file. Let me know.
[1] /home/parallels
Revision history for this message
|
#4 |
I ran that file but didn't get any result.
(base) parallels@
(base) parallels@
Revision history for this message
|
#5 |
Even without any errors?
Can you do "cat run_rivet.sh; ls;" in [1] and show me what your terminal says?
[1] ~/Downloads/
Revision history for this message
|
#6 |
Thank you for your help.
This is the result(base) parallels@
#!/usr/bin/bash
export PATH=/home/
export PATH=/home/
export LD_LIBRARY_
export LD_LIBRARY_
export PYTHONPATH=
export PYTHONPATH=
/home/parallels
rivet.log tag_1_pts.dat
run_01_
run_rivet.sh tag_1_pythia8_
run_shower.sh tag_1_pythia8.log
tag_1_djrs.dat unweighted_
Revision history for this message
|
#7 |
can you see what's written in the "rivet.log" file?
Revision history for this message
|
#8 |
yes,this is the content.
The rivet Python module could not be loaded: are your PYTHONPATH and (DY)LD_LIBRARY_PATH set correctly?
Try running 'python -c "import rivet"' at the command line (or "import rivet" in a Python REPL)
Full error message:
No module named 'commands'
Revision history for this message
|
#9 |
Hi this just suggests that you likely have problem with rivet installation (or at least something is mixed up with python environment).
HEPTools/
Can you make sure you have your rivet installed successfully?
Revision history for this message
|
#11 |
Sorry I just checked HEPTools/
g++: error: .2-a+fp16+
g++: error: .2-a+fp16+
g++: error: unrecognized command line option ‘-n1’; did you mean ‘-n’?
g++: error: unrecognized command line option ‘-n1’; did you mean ‘-n’?
error: command '/usr/bin/g++' failed with exit code 1
make[2]: *** [Makefile:713: all-local] Error 1
make[2]: Leaving directory '/tmp/tmpfbwnoz
make[1]: *** [Makefile:441: install-recursive] Error 1
make[1]: Leaving directory '/tmp/tmpfbwnoz
make: *** [Makefile:562: install-recursive] Error 1
Finished RIVET installation
Can you help with this problem?
Provide an answer of your own, or ask Zhaowei Song for more information if necessary.