Dear Florian
I am implementing a SUSY model in SARAH (arXiv: 1701.04566). I took
help from the MRSSM file which you provided and that works and compiles
perfectly fine. In case of my model it is giving some error while compiling
with SPheno. The errors are the following
==================================================================
Boundaries_RNEU.f90:3946.58:
Real(dp)::vev,vevs(2),vev2,mgut,mudim,mudimNew,sigma(2),mt,mb,cosW,cosW2,sinW2
Error: Symbol 'mt' at (1) already has basic type of COMPLEX
Boundaries_RNEU.f90:3967.4:
cosW=Sqrt(cosW2)
Error: Symbol 'cosw' at (1) has no IMPLICIT type
Boundaries_RNEU.f90:3965.5:
cosW2=mw2/mZ2
Error: Symbol 'cosw2' at (1) has no IMPLICIT type
Boundaries_RNEU.f90:4112.36:
Call RunRGE(kont,0.001_dp,gA,gB,mGUT)
Error: Symbol 'mgut' at (1) has no IMPLICIT type
Boundaries_RNEU.f90:4099.10:
mudim=1000._dp**2
Error: Symbol 'mudim' at (1) has no IMPLICIT type
Boundaries_RNEU.f90:3966.5:
sinW2=1._dp-cosW2
Error: Symbol 'sinw2' at (1) has no IMPLICIT type
Boundaries_RNEU.f90:301.18:
mRLu2 = mlRu2input
Error: Symbol 'mlru2input' at (1) has no IMPLICIT type
====================================================================
I thought that the errors are stemming from the definition of the superpotential term
mT T.T (T being the triplet) and hence I changed the Boundary high scale input from
{mT, mTinput} to {mT, XmTinput}. But the problem still remains. I would really appreciate
if you could tell me where I need to modify in order to debug.

Best regards

Sabya

Hi,

I am sure Florian will see the error immediately, but let me make a suggestion: have you tried renaming the mT parameter? Perhaps there is a confusion with the top quark mass.

Cheers,
Avelino

Hi,

as Avelino said, the most probably problem is that you use MT for the triplet mass, while SPheno already occupies mt for the top quark mass. Since Fortran is not case-sensitive, this causes problems. You should try to use a more unique name like MTrip.

Cheers
Florian

Dear Avelino and Florian

Thanks for your help. It works fine now. I shall bug you
again if I stumble upon something else.

Best

Sabya

Hi

This question might be more relevant in the model implementation section but for the sake of continuation I am posting it here. In the SPheno.m of my model file I used TanBeta as a MINPAR entry, similar to that in MRSSM. However, TanBeta did not show up in the LesHouchesXXX_Low file while it does for the generic high scale input file. This happens for MRSSM also. Do I just have to remove TabBeta from the MINPAR entry and add it somewhere else, like EXTPAR?

Best

Sabya

Hi,

this is most likely just a problem with the generation of the input template. You should just try to add the value and run it.

Cheers,
Florian

Hi Florian

If I understood you correctly, I added the value of TanBeta in the SPheno.m file but it
still does not show up in the LesHouches_low input file. I am attaching the SPheno.m
file and I would appreciate if you could look into it.

Best

Sabya

Did you try to run SPheno? As I said, this is most likely just a problem with writing the _low file, but the parameter will be recognised it if you write it in block MINPAR.

Dear Florian

As I said earlier, TanBeta is not being written in the LesHouchesxxx_low file. When I ran
SPheno with the generic input file (say for MRSSM), it works absolutely fine. With the
low energy input (generated by assigning TanBeta=10 in SPheno.m and similar values
for other entries), SPheno shows the following error:
===========================================================================
NaN appearing in GToParameters180
At position 48
Note: The following floating-point exceptions are signalling: IEEE_INVALID_FLAG IEEE_UNDERFLOW_FLAG IEEE_DENORMAL
STOP Subroutine TerminateProgram
===========================================================================

I have not come across this error before. I would appreciate if you could point out the
reason behind this error.

Best

Sabya

Hi,

the attached input works fine for me for the MRSSM. Sure, in MINPAR no tanbeta was shown in the template, but it's not problem to add it just in this file.

Cheers
Florian