-
Notifications
You must be signed in to change notification settings - Fork 0
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
Jacobian factors #10
Comments
Let me try to go back to this. |
@scarlehoff I think that I now understand the origin of the ~54 factor. We must rescale the Vrap result by |
The factor works perfectly, although with this factor the agreement is a bit worse (now the agreement between apfel and vrap is at worst 1.2% instead of being below 1% all across -with 54.35-). |
Are all the input parameters the same between APFEL and Vrap? |
The pbarn conversion is fixed. The factors hardcoded in vrap now are all using the latest edition of the PDG (but this might not be the case for apfel!) |
OK, but are these values consistent between APFEL and Vrap? I'd say no (so this may explain the difference). Question: are you taking the value of |
Sorry - I see that the values are not as in APFEL, you've said this explicitly! |
Well, about DYE906, turns out that the fktable expect a jacobian factor computed with |
As reported in #6, cross sections computed with Vrap+PineAPPL differ from the available FK tables computed with APFEL+APFELComb. Here is a summary of my understanding.
with
with the Jacobian
One can change variables and write
with the Jacobian
This explains the factor observed by @scarlehoff in APFEL - Vrap agreement. #6. Note that the cross section computed by APFEL, and therefore encapsulated in the FK tables, is always consistent with the format of the data. The Jacobian factors are indeed included as multiplicative factors on top of the baseline computation performed by APFEL: for DYE605 here; for DYE866P here.
This is what I grasp from the documentation and from here and here. This fact makes me think that, once the
The text was updated successfully, but these errors were encountered: