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

CKM factor in K -> pi nu nu amplitude #185

Closed
girishky opened this issue Jun 20, 2022 · 8 comments
Closed

CKM factor in K -> pi nu nu amplitude #185

girishky opened this issue Jun 20, 2022 · 8 comments
Labels

Comments

@girishky
Copy link
Contributor

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*)

xi_t = flavio.physics.ckm.xi('t', 'sd')(par)

Shouldn't it be xi('t', 'ds') in the above to be consistent with flavio operator definition?

@DavidMStraub
Copy link
Contributor

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?

@girishky
Copy link
Contributor Author

Hi David, Thanks for reply. I agree with what you said. But my point is that in K -> pi nunu amplitude function, X is basically WC for s -> d transition

X = -( wc['CL_'+label] + wc['CR_'+label] ) * s2w

but the CKM factor that is multiplied by WC here

amp = xi_t * X # top contribution
is related to conjugate (d->s) transition.

For absolute value, I agree this won't matter. But imaginary part of amplitude (even square of it) would be different if X also contain complex phase due to NP. So shouldn't amplitude be amp = xi_t.conj() * X or amp = xi_t * X.conj() ?

@hoodyn
Copy link
Contributor

hoodyn commented Jun 22, 2022

I agree with @girishky. Simply taking imaginary part for different neutrino species is inappropriate. It is the same kind of error that has been reported in #138 for K0->ll'.

@DavidMStraub
Copy link
Contributor

But that's a different issue...

@girishky
Copy link
Contributor Author

Hi @hoodyn , even in cases where nu flavor is conserved, so that NP contribution can only rescales X function, the current flavio implementation has issue (imo).
The operator $(\bar s d )_{V-A} (\bar nu nu)_{V-A}$ comes with VtdVts* in the normalization but its WC (i.e. X) is being multiplied with VtsVtd*; but this ckm factor appears in normalization of conjugate operator $(\bar d s)_{V-A} (\bar nu nu)_{V-A}$. The results of this is that even a CP conserving NP will affect KL decay mode which it shouldn't.
people can crosscheck the above observation.

best,

@peterstangl
Copy link
Collaborator

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?

I agree with this as long as in

amp = xi_t * X # top contribution

the X is strictly real. However, I agree with @girishky that if X also has an imaginary part, then it does matter whether xi('t', 'sd') or xi('t', 'ds') is used.

I suggest to simply replace

xi_t = flavio.physics.ckm.xi('t', 'sd')(par)
xi_c = flavio.physics.ckm.xi('c', 'sd')(par)

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 peterstangl added the bug label Aug 3, 2022
@girishky
Copy link
Contributor Author

girishky commented Aug 4, 2022

@peterstangl Yes. This is better. Thanks.

best,

@peterstangl
Copy link
Collaborator

This issue has been fixed in PR #189.

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

No branches or pull requests

4 participants