Spheno error

Questions about the interface between SARAH and SPheno as well as the FlavorKit functionality
Post Reply
IVANIELA
Posts: 5
Joined: 7. Dec 2017, 19:51

Spheno error

Post by IVANIELA » 5. Nov 2018, 12:45

Hi!
I'm trying to run SM in SPheno and I'm getting the next error

ar -x [-ouTLsv] archive [file ...]
make[2]: *** [../lib/libSPhenoSM.a(Settings.o)] Error 1
make[1]: *** [bin/SPhenoSM] Error 2
make: *** [bin/SPheno] Error 2



I tried installing SPheno again but It didn't work.

Have someone an idea about what I'm doing bad? Could it be a problem of Fortran?

Many Thanks!

FStaub
Site Admin
Posts: 822
Joined: 13. Apr 2016, 14:05

Re: Spheno error

Post by FStaub » 5. Nov 2018, 18:53

Sorry, I haven't seen that before. Maybe, another Mac specific problem?!

IVANIELA
Posts: 5
Joined: 7. Dec 2017, 19:51

Re: Spheno error

Post by IVANIELA » 5. Nov 2018, 20:38

Yes, I founded the way to solve it in another post :D

http://stauby.de/sarah_userforum/viewto ... ?f=4&t=444


Nevertheless, I continue having a problem. The SM runs perfectly but my new model is giving to me this error when I try to do the "Make Model=TTTDM"

...
gfortran -c -g -ffree-line-length-none -J../include -I../include TwoLoopMasses/2LPole_TTTDM.f90
TwoLoopMasses/2LPole_TTTDM.f90:101:13:

If (Abs(MTsI2/Qscale).lt.TwoLoopRegulatorMass) MTsI2=Qscale*TwoLoopRegulatorMass
1
Error: Symbol ‘mtsi2’ at (1) has no IMPLICIT type
make[2]: *** [../lib/libSPhenoTTTDM.a(2LPole_TTTDM.o)] Error 1
make[1]: *** [bin/SPhenoTTTDM] Error 2
make: *** [bin/SPheno] Error 2



any suggestions?


Thanks for all!

AForster
Posts: 7
Joined: 17. May 2019, 16:53

Re: Spheno error

Post by AForster » 1. Jul 2019, 10:16

Hi all. I am having a very similar error. I removed the -U but still got this "no implicit type" error. Any suggestions would be great!

Adam

FStaub
Site Admin
Posts: 822
Joined: 13. Apr 2016, 14:05

Re: Spheno error

Post by FStaub » 1. Jul 2019, 20:08

Hi,

looks strange. I can't say much without checking the model files. The question is: are you using the two-loop mass correction at all? Or do you assume that a on-shell renormalisation is possible (as most people do for non-susy models) and you are just checking tree-level masses? In the second case, you can turn off the output of the two-loop masses and the error should disappear.

Cheers,
Florian

Post Reply