-
Notifications
You must be signed in to change notification settings - Fork 7
Fix LHA VFNS SV benchmark #218
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
Closed
Closed
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
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?$\alpha_s$ running...
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.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes this is really strange. Moreover you are rescaling them by
xifsquared 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.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think masses are squared as well
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Indeed they are:
eko/src/eko/runner/legacy.py
Line 75 in 4f9920f
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Note that this has indeed no impact in FFNS, as masses are there either 0 or$\infty$ , and thus is not discussed by our scheme B check
Uh oh!
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is also consistent with what we have in benchmarks:
eko/benchmarks/eko/benchmark_strong_coupling.py
Line 443 in 4f9920f
the other place where
Couplingsis called is inmsbar_masses.py, but since SV with\bar{MS}masses are not supported, that should be it.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Discussing with @felixhekhorn we convinced ourselves that whatever we do for
alpha_sin 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 ) ineko==0.10all the masses were shifted in this way, including also scheme B. In particular, in scheme B we haveas1that 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 ineko==0.12is now bugged. Do you agree?There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
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, dividingm^2 / xif ^2is actually equivalent to multiplymu^2 * xif^2 = mu_f ^2which in fact is the factorization scale.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes I agree on both counts