scale setting in calculation of low energy observables

Questions about the interface between SARAH and SPheno as well as the FlavorKit functionality
Post Reply
WojciechKotlarski
Posts: 16
Joined: 15. Mar 2017, 11:47

scale setting in calculation of low energy observables

Post by WojciechKotlarski » 2. Oct 2017, 21:26

Hi Florian,

I have a question about how the parameters are run to the scale at which the low energy observables are computed. In CalculateLowEnergyConstraints subroutine you first run to the top scale and calculate quark-related observables. Then you run to the mZ to do the same for the lepton ones. The thing that confuses me is that every time you invoke the RunSM_and_SUSY_RGEs subroutine it sets globally the scale, which can be obtained back by the function getRenormalizationScale(). This scale is used internally by RunSM_and_SUSY_RGEs to determine, at which scale the input parameters are passed to that routine (you only pass the targe scale). The moment you invoke RunSM_and_SUSY_RGEs to run to the mZ scale it take the SUSY scale parameters but inteprets them as given at the scale of 160 GeV. If I put now instead of mZ a 1 TeV (and I'm using SPA convention [flag 2 =1]) I'm not getting back the 1 TeV parameters. Am I missing something or should there be a reset of scale before the second RunSM_and_SUSY_RGEs invocation?

cheers,
Wojciech

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

Re: scale setting in calculation of low energy observables

Post by FStaub » 3. Oct 2017, 15:03

Hi,

wow, you dug really deep into the code. It seems that you are correct, there is a re-setting of the scale missing before the call of the second running to M_Z. It should read

Code: Select all

!-------------------------------------
! running to M_Z 
!-------------------------------------

scalein = SetRenormalizationScale(scale_save**2) 

Call RunSM_and_SUSY_RGEs(mz,g1input,g2input,g3input,Ydinput,Yeinput,Yuinput,          & 
...
It seems that this has dropped out already some time ago and was never recognized (most likely because it 'only' affects the LFV observables). So, thanks a lot for pointing it out!

Cheers,
Florian

Post Reply