- “Matching to running parameters” (high-scale version)
Here, the syntax is shown asCode: Select all
DEFINITION[MatchingConditions] = { {Ye, YeSM}, {Yd, YdSM}, {Yu, YuSM}, {g1, g1SM}, {g2, g2SM}, {g3, g3SM}, {v, vSM} }; - “Matching to on-shell parameters” (low-scale version)
Here, on the other hand, a different definition is used:Code: Select all
BoundaryLowScaleInput = { {v, vSM}, {Ye, YeSM}, {Yd, YdSM}, {Yu, YuSM}, {g1, g1SM}, {g2, g2SM}, {g3, g3SM}, {\[Lambda], LambdaIN} };
Code: Select all
Matching::NotDefined: No matching conditions defined: The ones for a THDM type-II are used by default.“SM/SPheno.m” uses the first version:
Code: Select all
BoundaryLowScaleInput={
{\[Lambda],LambdaIN}
};
DEFINITION[MatchingConditions]=
{{v, vSM},
{Ye, YeSM},
{Yd, YdSM},
{Yu, YuSM},
{g1, g1SM},
{g2, g2SM},
{g3, g3SM}};
Code: Select all
BoundaryLowScaleInput={
{v, vSM},
{Ye, YeSM},
{Yd, YdSM},
{Yu, YuSM},
{g1, g1SM},
{g2, g2SM},
{g3, g3SM},
{\[Lambda],mHInput^2/(vSM^2)}
};
What exactly is the difference between the two versions? What should I use if I am interested in the low-scale version? Can I ignore the “Matching::NotDefined” message?