I recently noticed that the fermion mass running function get_m (in flavio/physics/edms/common.py) appears to be calling the down quark running mass for an up quark input, and vice versa:
def get_m(par, f, scale, eft):
...
if f == 'u':
return flavio.physics.running.running.get_md(par, scale, nf_out=nf_out)
elif f == 'd':
return flavio.physics.running.running.get_mu(par, scale, nf_out=nf_out)
...
My apologies if this is a silly question, but I'm unsure why this should be the case, especially in light of get_m's subsequent implementation in the function edm_f (where context suggests it should be providing the mass of the input fermion f). Any clarification would be much appreciated.
Dear authors,
I recently noticed that the fermion mass running function
get_m
(in flavio/physics/edms/common.py) appears to be calling the down quark running mass for an up quark input, and vice versa:My apologies if this is a silly question, but I'm unsure why this should be the case, especially in light of
get_m
's subsequent implementation in the functionedm_f
(where context suggests it should be providing the mass of the input fermionf
). Any clarification would be much appreciated.Thank you for your time. Ewan Wallace