Decay tables to pythia fails -- answered
Bug #961813 reported by
Pablo
This bug report was converted into a question: question #191406: Decay tables to pythia fails.
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
MadGraph5_aMC@NLO |
Invalid
|
Undecided
|
Johan Alwall |
Bug Description
Hello
I created an mssm custom model
Just used a spectrum generator and calculated the param_card with the tool provided in the web.
Also I had to comment the line defining the model, cause it gave some error (modsel[1] should be 1)
The point is that when calling Pythia, Pythia is taking propperly the spectrum in the param card, but not the decays, so it changes ny custom model decays
How would I fixed?
Thak you
Pablo
To post a comment you must log in.
Hello Pablo,
For MSSM, Pythia usually knows how to calculate branching ratios, and if it's allowed to use its own decay tables the decay kinematics are better treated (since it knows the interaction structure of the different decays). If your own branching ratios are used, Pythia will simply do isotropic decays. Having said that, it is easy to change the behavior: Either
1) avoid starting the model name with "mssm" (then branching ratios should be automatically read from the event file header)
2) Set IMSS(22)= 24 in the pythia_card.
Please let us know if this doesn't work.
All the best,
Johan