Fix LHA VFNS SV benchmark#218
Conversation
| order=new_theory.order, | ||
| method=couplings_mod_ev(new_operator.configs.evolution_method), | ||
| masses=masses, | ||
| masses=np.array(masses) / new_theory.xif**2, |
There was a problem hiding this comment.
This is changing everything, and in particular also the MHOU computed by @andreab1997
In principle, if it was a bug is a good thing. But why do you believe this should be so general?
I'm not sure why, if I change the factorization scale, the quark masses values should change in the
There was a problem hiding this comment.
Yes this is really strange. Moreover you are rescaling them by xif squared but the masses seem to be linear. If this fixes the benchmark, it suggestes a bug somewhere else...
There was a problem hiding this comment.
I think masses are squared as well
There was a problem hiding this comment.
Note that this has indeed no impact in FFNS, as masses are there either 0 or
There was a problem hiding this comment.
This is also consistent with what we have in benchmarks:
the other place where Couplings is called is in msbar_masses.py , but since SV with \bar{MS} masses are not supported, that should be it.
There was a problem hiding this comment.
Discussing with @felixhekhorn we convinced ourselves that whatever we do for alpha_s in scheme A we should do exactly the same in scheme B. In fact, there is no reason to do different things for the two schemes in that they are doing basically the same evolution (the only difference being that scheme A is using the varied splitting functions and scheme B is not). Note that (according to @felixhekhorn ) in eko==0.10 all the masses were shifted in this way, including also scheme B. In particular, in scheme B we have as1 that is used (correctly) for both the evolution and the "additional sv term" and we actually need to compute it rescaling the masses (as we were doing before). So, according to us, scheme B in eko==0.12 is now bugged. Do you agree?
There was a problem hiding this comment.
Of course we still need to understand why we should rescale the masses but this is not something new. My current hypothesis is that, since the masses always enter as ratio like m^2 / mu^2, dividing m^2 / xif ^2 is actually equivalent to multiply mu^2 * xif^2 = mu_f ^2 which in fact is the factorization scale.
There was a problem hiding this comment.
Yes I agree on both counts
|
@felixhekhorn, should we remove all the |
|
If this is recognized as a clear bug, we can merge this as a bug fix also without a clear reason, but consistently for any scheme (and if possible removing all However, in case open a further dedicated issue, please. Identifying the reason is extremely relevant to be sure we are acting correctly and consistently. |
About this, @felixhekhorn Have you tried running the test rescaling the scales (so multiplying them by |
|
Close in favor of #222 |
Closes #215
The fix here mirrors the original behaviour in
eko/src/eko/couplings.py
Lines 445 to 453 in d32b95a
I wonder whether we need to guard this division by scheme A ...