MadSpin branching ratio
Hi Olivier and all MG team,
I have one question regarding the branching ratio calculated using MadSpin along with MadGraph.
I am using model card in [1] with the run config card like below :
import model EffLRSM_NLO
generate p p > n2 n2 QCD=0 [QCD]
output PairProduction_
launch
shower=OFF
madspin=ON
0
set param_card mn2 300
set param_card mzr 1000
set param_card mwr 5000
set param_card mn1 1.000000e+14
compute_widths zr
compute_widths n2
compute_widths wr+
compute_widths wr-
set nevents 20000
set run_card pdlabel lhapdf
set run_card lhaid 306000
set run_card reweight_scale False
set no_parton_cut
0
(I run it after saving the lines above as "run_config.dat" and "./bin/mg5_aMC run_config.dat")
with MadSpin default card set as below (in the Template/
set Nevents_
set max_weight_ps_point 400 # number of PS to estimate the maximum for each event
set max_running_process 100
set spinmode none
define q = j t t~ b b~
decay n2 > mu q q
launch
With the settings like above, I expect the process where zr is produced and then decay into 2 pair of n2 and this n2 both decays into muons with jets (from wr).
The problem is that n2 > mu j j branching ratio is theoretically 1.0 and so I expected that the
crosssection(p p > n2 n2) = crosssection(p p > n2 n2) * BR(n2 > mu j j ) * BR(n2 > mu j j)
But looking at the results I have, the BR are somewhat different from 1., sometimes even bigger than 1. which does not physically make sense.
Is this again the use of nwa causing this problem?
We would prefer to take crosssection(p p > n2 n2) as our signal cross sections rather than BR multiplied ones but still we think it's better if we have understanding on this issue.
Thanks in advance,
Sihyun Jeon.
Question information
- Language:
- English Edit question
- Status:
- Solved
- Assignee:
- No assignee Edit question
- Solved by:
- Olivier Mattelaer
- Solved:
- Last query:
- Last reply: