Input vs. Output at tree level

Questions about the interface between SARAH and SPheno as well as the FlavorKit functionality
Post Reply
SDrau
Posts: 14
Joined: 21. Feb 2018, 14:54

Input vs. Output at tree level

Post by SDrau » 9. May 2018, 14:24

Hello,

I have a question about comparing the input vs. output at tree level. What I have tried looking at is essentially the potential of the two Higgs doublet model in the Higgs basis. I do have some of the tree level expressions relating physical quantities to the input parameters at tree level. I would expect to get back what I put in when the loop corrections to the masses are turned off. Yet, I see some deviations. I have attached a plot comparing FlexibleSUSY vs. SPheno vs. y=x line. In the plot, I scan over the mass of the heavier scalar Higgs and have the mixing angle between the light and heavier Higgses set to zero. Also, for the same parameter point, the mass of the lightest (preferably physical) Higgs also differs by ~20 GeV (not attached). Just in case, I have also attached the model files.

So the question would be, what might cause this and where should I be looking? I did try to fiddle with the flags, but without any luck so far.
If more information is needed I am happy to provide it.
Thanks in advance!

Regards,

Simonas
Attachments
SPhenoAndFS312.zip
(58.49 KiB) Downloaded 169 times

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

Re: Input vs. Output at tree level

Post by FStaub » 11. May 2018, 13:25

Hi,

the different flags were a bit messy so far and if they are not set in a specific way one-loop corrections to VEVs were included (what's correct at the given order of perturbation theory). I have now cleaned that up in v 4.13.0 which I uploaded this morning. See also the change-log.
I hope that works now.

Cheers,
Florian

SDrau
Posts: 14
Joined: 21. Feb 2018, 14:54

Re: Input vs. Output at tree level

Post by SDrau » 11. May 2018, 16:43

Hello,

I have downloaded the new version and included the new 19th flag but the deviation remains.
Maybe you could specify the special combination of flags so that I can try it out?

Regards,

Simonas

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

Re: Input vs. Output at tree level

Post by FStaub » 14. May 2018, 07:44

Hm... Strange.
The flags depent to some extent how you wrote Spheno.m. Therefore, I hope to avoid that huddle now by the new settings.
I can check if you post the model.

Cheers
Florian

SDrau
Posts: 14
Joined: 21. Feb 2018, 14:54

Re: Input vs. Output at tree level

Post by SDrau » 14. May 2018, 09:15

I have attached the model and thank you for having a look.

Regards,

Simonas
Attachments
SPheno312.zip
(3.93 KiB) Downloaded 144 times

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

Re: Input vs. Output at tree level

Post by FStaub » 14. May 2018, 12:49

Ok, it seems that there was I misunderstanding. I thought you calculate the parameters internally from the masses as input (as in the attached file done for a THDM-II). In your case, I guess that there might be a numerical difference in the VEV which you use in your calculation ind which SPheno uses. Did you check that?

Cheers,
Florian
Attachments
SPheno_MassInput.m
(1.88 KiB) Downloaded 169 times

SDrau
Posts: 14
Joined: 21. Feb 2018, 14:54

Re: Input vs. Output at tree level

Post by SDrau » 14. May 2018, 13:15

Sorry for the misunderstanding and thank you for pointing in the right direction! Turns out, that I had introduced typos in the block SMINPUTS, when making a scanning package...now it all matches nicely. Thanks again!

Regards,

Simonas

Post Reply