SPheno output as param_card.dat: Missing block: fralpha

Hi Roberto,

Concerning those warning:

> WARNING: For model consistency, update mass with id [1000014] to value 2002.51401 since it should be equal to parameter with id [1000012]
> WARNING: For model consistency, update mass with id [2000003] to value 2061.9168 since it should be equal to parameter with id [2000001]
> WARNING: For model consistency, update mass with id [1000003] to value 2047.85484 since it should be equal to parameter with id [1000001]
> WARNING: For model consistency, update mass with id [2000013] to value 2004.51351 since it should be equal to parameter with id [2000011]
> WARNING: For model consistency, update mass with id [1000013] to value 2001.06075 since it should be equal to parameter with id [1000011]
> WARNING: For model consistency, update mass with id [1000004] to value 207.098441 since it should be equal to parameter with id [1000002]
> WARNING: For model consistency, update mass with id [2000004] to value 2062.77625 since it should be equal to parameter with id [2000002]

You should use the mode MSSM_SLHA2-full which does not assume such symmetry.

Concerning:

> Missing block: fralpha

They are a convention problem between SLHA1/2 and UFO model.
The Block alpha does not have the same parser as the other block.
The FeynRules author have therefore replace the alpha block by the “fralpha” block.

The alpha block is formatted like this
Block ALPHA
        VALUE
while the fralpha block is formatted like this:
Block FRALPHA
        1 VALUE

Should be easy enough to change from one to the other. (I might think to add this as a functionality of the question)

Cheers,

Olivier

> On Nov 4, 2017, at 10:47, Roberto Franceschini <email address hidden> wrote:
>
> New question #660328 on MadGraph5_aMC@NLO:
> https://answers.launchpad.net/mg5amcnlo/+question/660328
>
> Hi,
> I am generating a spectrum for the MSSM with SPheno (v. 4.0.3) from the MSSM of SARAH (v. 4.11.0). The SPheno parameters 78 and 520 have been put to the values that I think make it compliant with MG card reader
>
> 78 1 # Output for MadGraph (writes also vanishing blocks)
> 520 0 # Write effective Higgs couplings (HiggsBounds blocks): put 0 to use file with MadGraph!
>
> Despite this when I load the card on a process that I generated from the MG model MSSM_SLHA2 shipped with v. 2.6.0 I get this error
>
> Missing block: fralpha
>
> The whole error is
> WARNING: For model consistency, update mass with id [1000014] to value 2002.51401 since it should be equal to parameter with id [1000012]
> WARNING: For model consistency, update mass with id [2000003] to value 2061.9168 since it should be equal to parameter with id [2000001]
> WARNING: For model consistency, update mass with id [1000003] to value 2047.85484 since it should be equal to parameter with id [1000001]
> WARNING: For model consistency, update mass with id [2000013] to value 2004.51351 since it should be equal to parameter with id [2000011]
> WARNING: For model consistency, update mass with id [1000013] to value 2001.06075 since it should be equal to parameter with id [1000011]
> WARNING: For model consistency, update mass with id [1000004] to value 207.098441 since it should be equal to parameter with id [1000002]
> WARNING: For model consistency, update mass with id [2000004] to value 2062.77625 since it should be equal to parameter with id [2000002]
> Command "generate_events " interrupted with error:
> MadGraph5Error : Invalid restriction card (not same block)
> set(['imyu', 'umix', 'minpar', 'snumix', 'uulmix', 'imuelmix', 'finetuning', 'imuurmix', 'sphenolowenergy', 'msoft', 'msu2', 'nmix', 'flavorkitqfv', 'imye', 'imyd', 'loopmsoft', 'imte', 'gauge', 'immsq2', 'lsp', 'immsu2', 'msd
> 2', 'chargemix', 'phases', 'sminputs', 'msl2', 'decay', 'higgslhc14', 'tu', 'selmix', 'imudlmix', 'immsd2', 'higgslhc13', 'imsnumix', 'higgslhc8', 'effhiggscouplings', 'immsl2', 'imudrmix', 'imuermix', 'imselmix', 'td', 'te', 'higgslhc7',
> 'imtd', 'usqmix', 'imfwcoef', 'imuulmix', 'uelmix', 'spheno', 'imnmix', 'fwcoef', 'msq2', 'higgsfcc100', 'dsqmix', 'imhmix', 'yd', 'immsoft', 'imtu', 'modsel', 'treemsoft', 'yu', 'mse2', 'pseudoscalarmix', 'imvmix', 'ye', 'gaugegut', 'uu
> rmix', 'immse2', 'udlmix', 'extpar', 'imumix', 'imusqmix', 'vmix', 'udrmix', 'imphases', 'mass', 'imdsqmix', 'uermix', 'flavorkitlfv', 'hmix', 'scalarmix']) != set(['umix', 'msoft', 'msu2', 'fralpha', 'msd2', 'msl2', 'decay', 'tu', 'selmi
> x', 'td', 'te', 'usqmix', 'dsqmix', 'ye', 'yd', 'sminputs', 'yu', 'mse2', 'nmix', 'vmix', 'msq2', 'mass', 'hmix']).
> Missing block: fralpha
> Unknown block : imyu,finetuning,minpar,snumix,uulmix,imuelmix,imuurmix,sphenolowenergy,fwcoef,imye,imyd,loopmsoft,gauge,immsq2,lsp,immsu2,effhiggscouplings,chargemix,phases,imfwcoef,uermix,udrmix,higgslhc14,imudlmix,flavorkitq
> fv,immsd2,higgslhc13,imnmix,higgslhc8,immsl2,imuermix,higgslhc7,imtd,imte,imselmix,imuulmix,uelmix,spheno,imsnumix,imudrmix,higgsfcc100,imhmix,immsoft,imtu,modsel,pseudoscalarmix,imvmix,gaugegut,uurmix,immse2,udlmix,extpar,imumix,imusqmix
> ,treemsoft,imphases,imdsqmix,flavorkitlfv,scalarmix
> Please report this bug on https://bugs.launchpad.net/mg5amcnlo
> More information is found in 'ME5_debug'.
> Please attach this file to your report.
>
> Am I too naive to think that the SLHA should allow me to generate the spectrum with SPheno and dump the whole card as a param_card.dat? did I miss any setting to make a good card?
>
> Thanks for helping,
> Roberto
>
>
>
>
>
>
> --
> You received this question notification because you are an answer
> contact for MadGraph5_aMC@NLO.

Dear Olivier, thanks for your reply. Let me update on what happnes running stop pair production on the MSSM_SLHA-full from a SPheno output card.

At first it complains

WARNING: information about "fralpha [1]" is missing (full block missing) using default value: -0.1138252.
WARNING: information about "hmix [2]" is missing using default value: 9.748624.
WARNING: information about "hmix [4]" is missing using default value: 166439.1.
WARNING: information about "upmns [1, 1]" is missing (full block missing) using default value: 1.0.
WARNING: information about "upmns [2, 2]" is missing (full block missing) using default value: 1.0.
WARNING: information about "upmns [3, 3]" is missing (full block missing) using default value: 1.0.
WARNING: information about "vckm [1, 1]" is missing (full block missing) using default value: 1.0.
WARNING: information about "vckm [2, 2]" is missing (full block missing) using default value: 1.0.
WARNING: information about "vckm [3, 3]" is missing (full block missing) using default value: 1.0.

"fralpha [1]" can be filled adding the block by hand, my only question is what paramters is that. I assumed that this is the angle between mass and gauge eigenstates in the Higgs sector, that is Block HMIX(11). But I may be wrong.

"hmix [2]" is TanBeta (which is an input for me) I have filled them in by hand
"hmix [4]" is mA^2(Q) (which is an input for me) I have filled them in by hand

With these "by hand" additions the calculation starts :) but the cross-section is 10^-71 pb ... not good.

I have inspected the LHEF and I see that it contains PID 1000006. So I have changed by hand the mass of that particle to something lower to see now a cross-section 10^67. Not good.

The issue for the PID of the produced particle may be another SLHA2 issue, but it is hard for me to say from which side.
If you look at eq.(29) of 0801.0045 and Table 2, the PID depends on the user decision on CPV, RPV, FLV. The card I was using has indeed 1000002 as lightest mass eigenstate, as eq.(29) implies, but I made them using a CP, RP, Flavor conserving input (MODSEL 3,4,5,6 all put to 0) so maybe the issue is on SPheno side. In any case coherently with that SPheno output contains a USQMIX whose "1 6" element is 9.96689049E-01, that is almost 1 hence the lightest is essentially a stop flavor.

I am rather puzzled about why the cross-section can be so small ...

Thanks for helping,
Roberto

Thanks for helping,
Roberto

This question was expired because it remained in the 'Open' state without activity for the last 15 days.

Hi Roberto,

Just to let you know that I have implemented a trigger to automatically convert the "alpha" block to "fralpha" block when relevant.
I have done this at two place in the code to try to be robust but with such type of auto-conversion, you are never fully robust.
So my recommendation will still be to do those change in advance.

Cheers,

Olivier