Problems with parsing of SLHA files

[Juergen Reuter]

When parsing an SLHA file, there are two problems: 1) WHIZARD chokes over the following:

** Fatal error: SLHA: block 'DCINFO' not found
WHIZARD run aborted.

A missing block DCINFO should not be considered a fatal error.

2) For the NMSSM, at least NMSSMtools produces the following lines

# GAUGE AND YUKAWA COUPLINGS AT THE GUT SCALE
BLOCK GAUGE Q=MGUT=  2.29965914E+16 # (GUT SCALE)
        1     7.15161543E-01   # g1(MGUT,DR_bar), GUT normalization
        2     7.15161543E-01   # g2(MGUT,DR_bar)
        3     7.04752503E-01   # g3(MGUT,DR_bar)
BLOCK YU Q=MGUT=  2.29965914E+16 # (GUT SCALE)
 3  3     1.26605005E+00   # HTOP(MGUT,DR_bar)
BLOCK YD Q=MGUT=  2.29965914E+16 # (GUT SCALE)
 3  3     1.77039818E-02   # HBOT(MGUT,DR_bar)
BLOCK YE Q=MGUT=  2.29965914E+16 # (GUT SCALE)
 3  3     2.12870330E-02   # HTAU(MGUT,DR_bar)

WHIZARD chokes over this with the error message

 Line 113: BLOCK NMSSMRUN Q=MGUT=  2.29965914E+16 $
 Expected syntax: SEQUENCE    <qvalue> = <qname> '=' <real>
 Found token: IDENTIFIER: 'MGUT'
*** Fatal error:  Syntax error in textual inpu

Also, it is clear what happens here, I leave this problem to Wolfgang as he can solve this fastest.

[kilian]

1) agreed.

2) can be solved, but is this syntax really compatible with SLHA?

[Juergen Reuter]

The second point has been discussed with Ulrich Ellwanger and Cyril Hugonie at Orsay on the 17th November. They will move the " = MGUT" as a remark with a # to the end of the corresponding lines in the new version of NMSSMtools.

[kilian]

Fixed in changeset [1301]. I added user options ?slha_read_decays etc. which decide which part of SLHA should be expected. Default is now not to read decay info (which is not used anyway, so far). Furthermore, a missing info block does no longer crash the program. This solves part 1).

Part 2) is a non-standard implementation in NMSSMtools, which will be fixed by the authors.

[Juergen Reuter]

Milestone v2.0-beta deleted