Incomplete/missing blocks in SLHA file output in SPheno

[MTalz]

Hi Florian,

I'm currently computing the fine-tuning measure with SARAH-4.12.2 interfaced with SPheno-3.3.8 in the high-scale MSSM. There appears to be an issue with some SLHA files output as incomplete, only containing information up to the Block VMIX. I have attached an example of such a file.

Here is my SPhenoInput Block:

Block SPhenoInput # SPheno specific input
1 0 # error level
2 0 # SPA conventions
7 0 # Skip 2-loop Higgs corrections
8 1 # Method used for two-loop calculation
9 1 # Gaugeless limit used at two-loop
10 1 # 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.0E+16 # fixed GUT scale (-1: dynamical GUT scale)
32 0 # Strict unification
34 1.000E-04 # Precision of mass calculation
35 100 # Maximal number of iterations
36 20 # Minimal number of iterations before discarding points
37 1 # Set Yukawa scheme
38 2 # 1- or 2-Loop RGEs
50 1 # Majorana phases: use only positive masses (put 0 to use file with CalcHep/Micromegas!)
51 0 # Write Output in CKM basis
52 0 # Write spectrum in case of tachyonic states
55 1 # Calculate loop corrected masses
57 0 # Calculate low energy constraints
65 1 # Solution tadpole equation
75 1 # Write WHIZARD files
76 1 # Write HiggsBounds file
77 0 # Output for MicrOmegas (running masses for light quarks; real mixing matrices)
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 1 # Write parameter values at GUT scale
520 1. # 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
550 1. # Calculate Fine-Tuning
551 0. # One-loop Fine-Tuning

Thanks,

Matthew

[FStaub]

Hi Matthew,

I must admit that I have never seen that. Is there any error message (like a segfault?).

Cheers,
Florian