-
Notifications
You must be signed in to change notification settings - Fork 63
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
CKM factor in K -> pi nu nu amplitude #185
Comments
In the observables, only the absolute value or the square of the imaginary part of the amplitude enters. so it shouldn't matter whether it's the d->s or the s->d amplitude. Do you agree? |
Hi David, Thanks for reply. I agree with what you said. But my point is that in K -> pi nunu amplitude function, flavio/flavio/physics/kdecays/kpinunu.py Line 20 in 3d11de0
but the CKM factor that is multiplied by WC here flavio/flavio/physics/kdecays/kpinunu.py Line 24 in 3d11de0
For absolute value, I agree this won't matter. But imaginary part of amplitude (even square of it) would be different if |
But that's a different issue... |
Hi @hoodyn , even in cases where nu flavor is conserved, so that NP contribution can only rescales best, |
I agree with this as long as in flavio/flavio/physics/kdecays/kpinunu.py Line 24 in 3d11de0
the I suggest to simply replace flavio/flavio/physics/kdecays/kpinunu.py Lines 11 to 12 in 3d11de0
by xi_t = flavio.physics.ckm.xi('t', 'ds')(par)
xi_c = flavio.physics.ckm.xi('c', 'ds')(par) @DavidMStraub @girishky do you both agree with this solution? |
@peterstangl Yes. This is better. Thanks. best, |
This issue has been fixed in PR #189. |
Hi,
Flavio basis convention (https://wcxf.github.io/assets/pdf/WET-3.flavio.pdf) for s -> d nunu transition has CKM factor (Vts* Vtd) in operators' definition. But in flavio implementation, amplitude for K -> pi nu nu has
xi('t', 'sd')
which is basically (Vts Vtd*)flavio/flavio/physics/kdecays/kpinunu.py
Line 11 in 3d11de0
Shouldn't it be
xi('t', 'ds')
in the above to be consistent with flavio operator definition?The text was updated successfully, but these errors were encountered: