Skip to content
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

make sure that alphas and Q2 grids agree in alpha_s_bundle_pdf #2197

Open
RoyStegeman opened this issue Nov 4, 2024 · 2 comments
Open

make sure that alphas and Q2 grids agree in alpha_s_bundle_pdf #2197

RoyStegeman opened this issue Nov 4, 2024 · 2 comments

Comments

@RoyStegeman
Copy link
Member

RoyStegeman commented Nov 4, 2024

The Q2grid of the alphas variation members in NNPDF40_an3lo_as_01180_mhou_pdfas is different from the Q2grid (and number of points in the alphas grid) in the .info file. This means that alphas cannot be computed for the error members.

To avoid this in the future, it should be checked that these grids are consistent.

The error can be reproduced as follows:

>>> import lhapdf
>>> pdf = lhapdf.mkPDF("NNPDF40_an3lo_as_01180_mhou_pdfas/101")
>>> pdf.alphasQ2(10)

Which then raises the error

RuntimeError: AlphaS value and Q interpolation arrays are differently sized
@scarlehoff
Copy link
Member

What do you mean by that?

Is this related to this bug? NNPDF/eko#391 (the ekos prepared before the fix was merged would produce a wrong-ish info file)

@RoyStegeman
Copy link
Member Author

No, for NNPDF40_an3lo_as_01180_mhou_pdfas between mc and mb for members 101 and 102 the Q2 grid is
1.5100000E+00 1.6500000E+00 1.7874390E+00 1.9429050E+00 2.1193750E+00 2.3204100E+00 2.5502940E+00 2.8142020E+00 3.1184120E+00 3.4705780E+00 3.8800750E+00 4.3584520E+00 4.9200000E+00

while for members 0-100 it is
1.510000e+00 1.657384e+00 1.827949e+00 2.026319e+00 2.258232e+00 2.530851e+00 2.853170e+00 3.236569e+00 3.695538e+00 4.248669e+00 4.920000e+00

The AlphaS_Qs in the .info file is the same as the one for members 0-100, but obviously disagrees with what is there for members 101 and 102

Not sure why this happened originally, but it's something we can check for when combining multiple PDF sets into one.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants