-
Notifications
You must be signed in to change notification settings - Fork 2
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
Check predictions near threshold #173
Comments
@felixhekhorn, @andreab1997 do we still have this problem? |
I don't think this is due to the LHAPDF interpolation because the difference is seen even when not using LHAPDF but just inspecting the files. |
On a first naive attempt I can not reproduce this ...
with
where the last point in each |
You have many points that are above the per-mille error (which is my threshold) so this might be just a difference on what we consider an acceptable error. For instance: |
If I correctly read the corresponding APFEL function
|
This is exactly the reason why we are not performing automated comparison:
You should at least include both relative and absolute thresholds in your comparison, and yet it might not be enough to cover for all the known and not relevant quirks... |
You have problems also with bigger values:
As I said, if In any case what worries me is that Q=mb is singled out. |
There are cases in which we could considerably go down in discrepancy, but the different integration and interpolation procedure are putting some boundaries. Usually, we consider we have a problem if we have a consistently shifted behavior, while single points are not that relevant (that's why we struggled implementing this criterion in a piece of code - we tried, but it got too complex, especially in 2D, where we could have 1D defects).
Ok, this is worrying. But there are two different scenarios:
|
At nf=4 (i.e., below threshold): At nf=5, instead, many of the points at the threshold are wrong (so Q=4.92 GeV). As one gets farther away from the threshold less and less points are wrong... If I only look above 1e-7 then it's only Q=4.92 GeV. So everything wrong beyond the threshold seem to be also at very low x. In order to avoid looking at very small numbers dancing around 0 I set up an absolute tolerance (quite big) of 1e-5 which further removes points from the check but not all. Now, inspecting the rows one thing I'm noticing is that the PDF evolved with apfel has |
let me stress this point: in the above comparison we were using the degree-4 interpolation and an xgrid of I repeated the exercise with
which I consider an improvement ... moreover, remember that I run APFEL with
just as a reminder: EKO can deal with the singularity (because we can compute in either FNS), but APFEL can't |
Inspecting the numbers it seems that exactly at |
actually, I'm no longer sure about this, because |
I think this can be closed. The difference seem to be due to a difference in convention at exactly the quark thresholds. Previously the first point at |
I argue that is not a convention, and even APFEL is able to apply the matching properly. The only problem might be retrieving the correct result, and treat it separately, that was a problem also with EKO, before #242 (indeed we had custom mechanisms for getting it correct in special cases, like fitting scale or |
Follow up of https://github.com/NNPDF/fktables/issues/19
when the final scale is close to a threshold (typically the bottom threshold), we can see some discrepancy with the LHAPDF grids.
It was conjectured, this might be related to the lhapdf interpolation - we should check explicitly by comparing with apfel (to which we should match exactly) and LHAPDF with the same settings.
The text was updated successfully, but these errors were encountered: