Problem Executing MG5-2.5beta with SLHA2

[jackaraz]

Dear Florian,

I asked this question in MG5 launchpad https://answers.launchpad.net/mg5amcnlo ... ion/402462 but they redirected me to you instead. I'm trying to run the very same processes that I was running in MG5-2.4 which were giving me warning for imaginary matrices but still running it, as you already mentioned about this problem in one of the manuals. In the new version it's not running it at all. It basically doesnt read the SLHA2 file. Is it possible to somehow get a different output from SPheno that compatible with mg5?

Thanks
Best regards

My flags are as follows in LesHouches file:

Block SPhenoInput # SPheno specific input
1 -1 # error level
2 0 # SPA conventions
7 0 # Skip 2-loop Higgs corrections
8 3 # Method used for two-loop calculation
9 1 # Gaugeless limit used at two-loop
10 0 # safe-mode used at two-loop
11 1 # calculate branching ratios
13 1 # 3-Body decays: none (0), fermion (1), scalar (2), both (3)
14 0 # Run couplings to scale of decaying particle
12 1.000E-04 # write only branching ratios larger than this value
15 1.000E-30 # write only decay if width larger than this value
31 -1 # fixed GUT scale (-1: dynamical GUT scale)
32 0 # Strict unification
34 1.000E-04 # Precision of mass calculation
35 40 # Maximal number of iterations
36 5 # Minimal number of iterations before discarding points
37 1 # Set Yukawa scheme
38 2 # 1- or 2-Loop RGEs
50 0 # Majorana phases: use only positive masses (put 0 to use file with CalcHep/Micromegas!)
51 0 # Write Output in CKM basis
52 1 # Write spectrum in case of tachyonic states
53 1
54 1
55 1 # Calculate loop corrected masses
57 1 # Calculate low energy constraints
60 1 # Include possible, kinetic mixing
65 1 # Solution tadpole equation
75 0 # Write WHIZARD files
76 1 # Write HiggsBounds file
86 0. # Maximal width to be counted as invisible in Higgs decays; -1: only LSP
510 0. # Write tree level values for tadpole solutions
515 0 # Write parameter values at GUT scale
520 0. # Write effective Higgs couplings (HiggsBounds blocks): put 0 to use file with MadGraph!
521 1. # Diphoton/Digluon widths including higher order
525 0. # Write loop contributions to diphoton decay of Higgs
530 0. # Write Blocks for Vevacious

[FStaub]

Hi,

hmm.. I think this is a bit unfortune from MG side to force to have to write so many unnecessary parameters in the SLHA file. Can you try if the following works: editing InputOutput_UMSSM.f90 and change

Code: Select all

WriteNextBlock = .false.

to

Code: Select all

WriteNextBlock = .true.

everywhere. If that works out, I'll add a flag to turn this option on/off in the future.

Cheers,
Florian

[FStaub]

Btw., I couldn't resist to comment on that in the MG forum...

[jackaraz]

Dear Florian

Thanks for quick response, and actually thanks for not resisting. I tried what you suggested but, problem remains, In fact SPheno doesnt print Blocks with 0.0 inputs, It just prints block names such as:

SPheno.sps.UMSSM:

Code: Select all

...
   3    1.03212408E+00  # g3
   5    6.34108876E-01  # gp
Block IMGAUGE Q=  1.62757131E+03  # (SUSY Scale)
Block NMSSMRUN Q=  1.62757131E+03  # (SUSY Scale)
   1    4.97962522E-01  # lam
   3    9.95925044E+02  # Tlam
...

Sorry for the trouble.
Best regards
Jack

[FStaub]

Can you try to remove the line with IMGAUGE? The block is empty because all gauge couplings are real by definition.

[jackaraz]

Sure, but they are all like this. I'm attaching one of the results.

Best regards

[FStaub]

Hmm.. I don't understand that. For me, it looks like attached.
What compiler do you use?

[jackaraz]

I'm using gfortran in Ubuntu 14.04. it shouldnt make any difference does it? at least not while writing info to files i believe

[FStaub]

Yes, I also think that it is very unlikely to be a compiler issue. However, I don't have any other idea...

[FStaub]

Hi,

here is a beta version: https://flstaub.web.cern.ch/flstaub/SAR ... 2b2.tar.gz
Can you try that together with the flag

Code: Select all

 78 1 # Output for MG (Imaginary parts explicit)

in the LH input file.

Cheers,
Florian