Problems in recognizing a new parameter

Questions about the interface between SARAH and SPheno as well as the FlavorKit functionality
felipeagf
Posts: 33
Joined: 19. Jan 2017, 12:28

Re: Problems in recognizing a new parameter

Post by felipeagf » 4. Jun 2017, 17:28

Hi Florian

After imposing simple modifications in the standard SPheno.m file of UMSSM such as write all the new U(1) charges in terms of the new parameter ThetaE6 I managed to create the corresponding new binary SPhenoUMSSMmine for this model. But when I run SPheno using an input file (LesHouches.in.UMSSMmine) which is identical to the one I used in the standard binary SPhenoUMSSM SPheno shows some warning messages related to the routines Mhh and MAh as you can see in the figure here.

This is strange because the input file is equivalent to the low version standard one LesHouches.in.UMSSM that always works with the same flag configuration and parameter values, just differing in the Block EXTPAR where the parameter ThetaE6 is written in place of all charges as you can see in the attached files here. Why SPheno is not calculating the Higgs mass (and the other masses) in the same way as in the standard version. I also attached here all the new model files which were used by SARAH to understand this simple difference and create the SPheno input files.




Cheers
Felipe
Attachments
UMSSMmine.m
(3.22 KiB) Downloaded 206 times
particles.m
(10.13 KiB) Downloaded 181 times
parameters.m
(6.4 KiB) Downloaded 188 times
SPheno.m
(1.74 KiB) Downloaded 227 times
LesHouches.in.UMSSMmine.m
(6.85 KiB) Downloaded 199 times
LesHouches.in.UMSSM.m
(7.05 KiB) Downloaded 194 times
Captura de tela de 2017-06-04 17-11-59.png
Captura de tela de 2017-06-04 17-11-59.png (123.92 KiB) Viewed 9769 times

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

Re: Problems in recognizing a new parameter

Post by FStaub » 6. Jun 2017, 11:19

Hi,

the problem is that the charges are missing in the very first running between M_Z and M_SUSY because you define them at M_SUSY. So, either you define them via SPheno.m in BoundaryEWSBScale, or you add these lines by hand in Boundaries_UMSSMmine.f90 to the routine FirstGuess (line 3806):

Code: Select all

NameOfUnit(Iname)="FirstGuess" 

Qq = -Cos(ThetaE6)/(2._dp*sqrt(10._dp)) + Sin(ThetaE6)/(2._dp*sqrt(6._dp))
Ql = (3*Cos(ThetaE6))/(2._dp*sqrt(10._dp)) + Sin(ThetaE6)/(2._dp*sqrt(6._dp))
QHd = -(Cos(ThetaE6)/sqrt(10._dp)) - Sin(ThetaE6)/sqrt(6._dp)
QHu = Cos(ThetaE6)/sqrt(10._dp) - Sin(ThetaE6)/sqrt(6._dp)
Qd = (3*Cos(ThetaE6))/(2._dp*sqrt(10._dp)) + Sin(ThetaE6)/(2._dp*sqrt(6._dp))
Qu = -Cos(ThetaE6)/(2._dp*sqrt(10._dp)) + Sin(ThetaE6)/(2._dp*sqrt(6._dp))
Qe = -Cos(ThetaE6)/(2._dp*sqrt(10._dp)) + Sin(ThetaE6)/(2._dp*sqrt(6._dp))
Qv = -(Sqrt(5._dp/2._dp)*Cos(ThetaE6))/2._dp + Sin(ThetaE6)/(2._dp*sqrt(6._dp))
Qs = Sqrt(2._dp/3._dp)*Sin(ThetaE6)

felipeagf
Posts: 33
Joined: 19. Jan 2017, 12:28

Re: Problems in recognizing a new parameter

Post by felipeagf » 6. Jun 2017, 21:05

Hi Florian

Thank you very much for your reply. Now it works well and the spectrum seems to be (practically) equivalent to the standard case where all the charges are input parameters. The only thing that is missing now is a block in SPheno spectrum file that can show the value of the mixing angle parameter /ThetaE6 that was used in the calculation. I defined this new parameter in the parameters.m file in the following way

{\[Theta]E6, {Description -> "U(1) Mixing Angle",
LateX -> "{\\Theta}_{E6}",
Real -> True,
OutputName -> ThetaE6,
LesHouches -> U(1)MIXANGLE}},

but SPheno output does not show a block called U(1)MIXANGLE that includes the ThetaE6 parameter. What is missing in this case? How can I make SPheno write a block including the used value of this parameter?





Cheers
Felipe

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

Re: Problems in recognizing a new parameter

Post by FStaub » 7. Jun 2017, 09:49

Please use for these kind of questions the manual or the wiki in the future. On http://stauby.de/sarah_wiki/index.php?t ... rameters.m you find
LesHouches: defines the position of the parameter in a Les Houches spectrum file. For matrices just the name of the block is defined, for scalars the block and an entry has to be given: {block, number}.
Moreover, the name you are using is not a valid Fortran string, and the value of the angle already appears in EXTPAR, so there shouldn't be any need at all to get it again in another block.

felipeagf
Posts: 33
Joined: 19. Jan 2017, 12:28

Re: Problems in recognizing a new parameter

Post by felipeagf » 5. Jul 2017, 23:12

Hi Florian

I created an account in the ATLAS computer cluster BAF system of uni-bonn and followed all the necessary steps to run SPheno correctly as I've done with my own computers. After installing and unpacking the tool and creating a new directory of my model I copied all the necessary outputs of SARAH typing
cp $PATH/SARAH/Output/UMSSM/EWSB/SPheno/* UMSSM/.

All these steps seemed to word successfully. But when I typed make Model=UMSSM in the root directory of SPheno as should be done some unexpected strange messages appeared in such a way that can be seen in the image file attached here. This is weird because it never happens when I did the same in my own computers. When I run make in the root directory of SPheno it works, so why it cannot create a new binary of a new model?

In the Makefile of SPheno directory I put F90 = gfortran as the compiler to be used. Do you think that it is still missing some things in the ATLAS computer cluster BAF system that should be installed?




Cheers
Felipe
Attachments
EffPotFunctions.f90.m
(38.75 KiB) Downloaded 237 times
Makefile.m
(508 Bytes) Downloaded 223 times
Screenshot from 2017-07-05 22-57-12.png
Screenshot from 2017-07-05 22-57-12.png (238.81 KiB) Viewed 9755 times

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

Re: Problems in recognizing a new parameter

Post by FStaub » 6. Jul 2017, 10:54

Hi,

the gfortran compiler is outdated. You need at least 4.8.

Cheers,
Florain

Post Reply