Page 1 of 1

Question on low energy model

Posted: 12. Mar 2018, 23:33
by katelynn
Hi Florian,

I have a low energy model where 3 scalar doublets receive a vev but 2 of the vevs are proportional
so effectively there are only 2 vevs, I checked the model with CheckModel[] and there
seems not to be an apparent error. I'm interested in calculating the relic density of an
additional inert doublet with Micromegas, so I'm only considering tree level quantities.

When I do

MakeSPheno[IncludeLoopDecays -> False]

and try to compile I get this error:


gfortran -c -g -ffree-line-length-none -J../include -I../include SPheno4HDM_S3.f90
SPheno4HDM_S3.f90:223:19:

tanbetaMZ = tanbeta

Error: Symbol ‘tanbeta’ at (1) has no IMPLICIT type

I attach the model files, any suggestions?
I'm using SARAH 4.12.3 and SPheno 4.0.3

Thank you for your time.

Re: Question on low energy model

Posted: 13. Mar 2018, 19:19
by FStaub
Hi,

I guess the problem is that you use another OutputName for TanBeta. It seems that this possibility was not yet considered in SARAH before. Therefore, it should be sufficient to change TanBeta in that line to tb which you use.

Cheers,
Florian

Re: Question on low energy model

Posted: 14. Mar 2018, 04:46
by katelynn
Hi Florian,

ok thanks.

Still, it is a little bit confusing because in the parameters.m file located in
SARAH-4.12.3/Models directory, the definition of TanBeta also has

OutputName-> tb

Alternatively I also tried

OutputName-> tanbeta

and it compiles without errors.

Thanks a lot.

Re: Question on low energy model

Posted: 14. Mar 2018, 10:14
by FStaub
Hi,

that's a good observation and I was also confused right now. The point is that I actually don't parametrise the ew VEVs in the other model files via tan(beta) in parameters.m, but do that only via the matching conditions written in SPheno.m. Therefore, tan(beta) is not considered as an 'intrinsic' model parameter and the OutputName is not used.
I hope that became somehow clear. It's a picky discrimination how SARAH treats parameters internally. Maybe, I find a way how to circumvent that problem in the future.

Cheers,
Florian