Closed felixhekhorn closed 4 years ago
Hi @felixhekhorn but according to the PDF, Eq. (18.18), F3 depends only on q-qbar right? And we never have a non-zero charm asymmetry, at least at the input evolution scale
In your model conly is charm the same as anticharm or different? I am confused here
according to the PDF, Eq. (18.18),
are we talking about the same file? we meant this one: https://github.com/scarrazza/apfel/blob/master/doc/pdfs/CC_observables_def.pdf and there seems to be no equation (18.18)
And we never have a non-zero charm asymmetry, at least at the input evolution scale
maybe in a true physical setup, yes, but here we think of the PDF as an external property (of which we know nothing) (and also c and cbar can diverge at higher orders) ... so here for benchmarking purpose to isolate one feature from another, we've chosen the (unphysical) conly
with
In your model conly is charm the same as anticharm or different?
c=x(1-x), cbar=0=u=ubar=g=...
I meant the PDG ;)
It is true that for benchmarking purposes we can assume that c and cbar are different (although this will not happen in a realistic setup). In this case yes, APFEL should return a non-zero value, I agree. So this needs to be fixed, I guess that somewhere in APFEL one assumes that c_V=0?
@felixhekhorn from the banner I see that you are using the NF = 3 FFNS that assumes that there is no charm in the initial state. Therefore it is perfectly consistent that you get zero.
@felixhekhorn from the banner I see that you are using the NF = 3 FFNS that assumes that there is no charm in the initial state. Therefore it is perfectly consistent that you get zero.
I guess you're right -> it is a bug in our implementation
F3charm
with theconly
pdf (which is defined byc(x)=x(1-x)
and 0 otherwise ) APFEL is 0, while we're not (see table below)CC_observables_def.pdf
)F3charm
relies on the seperation of the CKM matrixoutput:
APFEL setup: