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

Errors in implementation of K0->ll' #138

Open
hoodyn opened this issue Jan 21, 2021 · 5 comments · May be fixed by #141
Open

Errors in implementation of K0->ll' #138

hoodyn opened this issue Jan 21, 2021 · 5 comments · May be fixed by #141
Labels

Comments

@hoodyn
Copy link
Contributor

hoodyn commented Jan 21, 2021

Hi,

I think I've found two problems in the implementation of K0->ll' in flavio/physics/kdecays/kll.py.

Lepton flavour violating K-short decay results in errors

K=KS together with l1 != l2 not a valid option in the definition of function amplitudes_eff:

   ...
    if K == 'KS' and l1 == l2:
        Peff = P.imag
        Seff = S.real + SLD
    if K == 'KL':
        Peff = P.real + PLD
        Seff = S.imag
    return Peff, Seff

Correspondingly, asking flavio for a prediction on BR(KS->emu,mue) leads to
UnboundLocalError: local variable 'Peff' referenced before assignment.

This would have been trivial to fix, be there not the second problem.

Lepton flavour violating K-long decay calculated incorrectly

This is physIcs-related issue: the formulas for using imaginary of real parts of the Wilson coefficients (or, of the P,S parts of the amplitudes in the current flavio implementation) hold only for the lepton flavour conserving case.

Generally, KL and KS are superpositions of K0 and antiK0: K_L,S = (sbar d +- dbar s) / sqrt(2).
Thus, naively, the amplitudes consist of the combinations (CX_sdl1l2 +- CX_dsl1l2)/sqrt(2) with X=9,9p,10,10p,S,SP,P,Pp.
However, in flavio, the _dsl1l2 Wilson coefficients are not to be specified as they are obtained from complex-conjugated _sdl2l1 ones. In particular:
image
(The extra minus sign for CS-CSp is spit by the CP transformation of the corresponding operator - I would appreciate if someone could check the above formulas independently. The CX + CXp combinations are irelevant for pseudoscalar meson decays.)
If l1==l2, one gets terms like ( (CX_sdll-CXp_sdll) +- (CX_sdll-CXp_sdll).conj() ) / sqrt(2) which simplify to real or i*imaginary parts indeed.
However, the LFV cases lead to expressions like ( (CX_sdemu-CXp_sdemu) +- (CX_sdmue-CXp_sdmue).conj() ) / sqrt(2) which obviously cannot be simplified any further.

Regards, Matej Hudec

@hoodyn
Copy link
Contributor Author

hoodyn commented Jan 21, 2021

If you agree, I would volunteer to do the repair, but I'm not sure about the policy: shall I fork the project, or will you give me the rights to set up a branch?

NB: in the formulas above, xi_t = V[t,s] V[t,d]* is the complex factor in the normalization coefficient of the effective operators.

@DavidMStraub
Copy link
Contributor

Hi,

while I am responsible for the implementation and it's definitely possible that your formulas are correct, unfortunately I don't have time to look into this in detail, so someone else would have to check it.

Concerning the repair: yes, it works with forking and pull requests, as usual.

@peterstangl
Copy link
Collaborator

peterstangl commented Jan 21, 2021

@hoodyn, I agree that the implementation has the two issues you have described. Thank you for reporting them and for your offer to fix them!

For implementing the modifications, you should fork the repository, create a new branch in the forked repository, commit your changes to this new branch, and then go to the main flavio repository on the GitHub website, where you will be able to open a "Pull Request" (PR). Once you have opened the PR, I will check the implementation before merging it into the main flavio repository.

@hoodyn hoodyn linked a pull request Feb 10, 2021 that will close this issue
@peterstangl peterstangl linked a pull request Mar 7, 2021 that will close this issue
@hoodyn
Copy link
Contributor Author

hoodyn commented Feb 18, 2022

Hi, has there been there any progress with verifying my PR during the least year? Is there something I can do in order to help proceed?

@peterstangl
Copy link
Collaborator

@hoodyn, yes, I actually went through most of your implementation and the derivation in the notes you provided (which was very helpful!). I noticed some issues in the implementation of the long-distant part but I had no time yet to completely finish all checks. I will comment on what I found so far in the PR as soon as I have time to look into this again (hopefully within the next couple of weeks).

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

Successfully merging a pull request may close this issue.

3 participants