-
Notifications
You must be signed in to change notification settings - Fork 18
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
implement exact relations between (v,Mh2) and (m2,Lambda) #59
implement exact relations between (v,Mh2) and (m2,Lambda) #59
Conversation
6ebfc0b
to
865b7d1
Compare
Pull Request Test Coverage Report for Build 219
💛 - Coveralls |
The check with Python 3.7 failes because:
|
I hope it is Ok that I chime in. |
@JoseEliel thank you for your comment! I'm not sure if I understand completely, why this PR would be a problem for what you want to do. First of all, at the moment, as far as I see, This being said, I do not understand how the modifications of this PR would change anything about the use cases you describe. One can still use the updated (Concerning the freedom of v != 246 GeV, this does actually not depend on gauge boson masses if the Fermi constant GF is used as input parameter for fixing v (as currently done in |
@jasonaebischerGIT, this problem is fixed by PR #60. Please merge #60 first. |
Thanks for the detailed reply. This is very helpful.
I think this is what I meant. I originally faced this issue when using smelli actually, and I was thinking about both codes when writing. Apologies for the confusion. I have tried (though admittedly in a 'hacky' way) to implement something like what you mention with my numerical procedure. My implementation goes like this: When lambda and m2 are found by vMh2_to_m2Lambda, what is found are the "best possible" values numerically within a given region of the lambda-m2 parameter space (in my case, for example, lambda < some value). I've been assuming that then those are the values used in the running (and checked that the smpars dictionary has stored the values found by the minimization). But this might be wrong though. I then just let Smelli do its thing and calculate likelihoods for EW precision tests and Higgs physics. I've gotten good likelihoods for points with a small lambda that would have come out with a larger lambda (but spot-on Higgs mass) otherwise. I'm not sure all of that is consistent, and I would really appreciate your input. If you think this is beyond what we should discuss here, I would be happy (and thankful) if you want to continue the discussion by mail or a short call. |
@JoseEliel I'm happy to discuss this further with you, I'm just not sure if our discussion fits here in this PR. I would suggest you open a new issue or we can also continue the discussion by email: stangl@itp.unibe.ch |
865b7d1
to
0109f59
Compare
This PR implements the exact relations between the physical Higgs VEV and mass and the parameters of the Higgs potential.
@jasonaebischerGIT, maybe you can check the relations. What I did was:
v2
in terms ofLambda
,Cphi
, andm2
.m2
to get an exact expression form2
in terms ofLambda
,Cphi
, andv2
Mh2
and eliminatem2
by using the exact expression form2
from above to get an exact expression forMh2
in terms ofLambda
,Cphi
,Ckin
, andv2
Lambda
to get an exact expression forLambda
in terms ofMh2
,Cphi
,Ckin
, andv2