REVIEW 2 cited by
Lepton Flavour Violating tau and mu decays induced by scalar leptoquark
Not yet reviewed by Pith; the record is open.
This paper has not been read by Pith yet. Machine review is queued; the pith claim, tier, and objections will appear here once it completes.
SPECIMEN: schema-true, not a live event
T0 review · schema-true
One-sentence machine reading of the paper's core claim.
pith:XXXXXXXX · record.json · timestamp
Signed reviews
abstract
We show that the scalar leptoquark Yukawa couplings generate a significant lepton flavour violation. We compute the light scalar leptoquark contributions to the branching ratios (Br) of the lepton flavour violating (LFV) decays $\ell \to \ell_i \ell_j \bar{\ell}_j$ and $\ell \rightarrow \ell^{\prime} \gamma$ with (i,j = e,$\mu$). We discuss the role of the relevant input parameters to these decay rates which are the Yukawa couplings ($h_{a\ell}$) with ($a=u,c,t$), the light scalar mass $M_{S_{1}}$ and the mixing angle $\sin2\theta_{LQ}$. We investigate the experimental limits from $(g-2)_\mu$, $\mu-e$ conversion and $\pi \to e \nu_e, \mu \nu_\mu$ to get constraint on the input parameter space. We predict that the upper limits on the branching ratios of $\tau \to \ell_i \ell_j \bar{\ell}_j $ can reach the experimental current limits. We also show that it is possible to accommodate both $\tau \to \ell_i \ell_j \bar{\ell}_j$ and $\tau \to \ell\gamma$ branching ratios for certain choices of LQ parameters.
Forward citations
Cited by 2 Pith papers
-
Constraints on scalar leptoquarks from lepton and kaon physics
Scalar leptoquark couplings are constrained by a comprehensive set of upper bounds from tau, muon, electron, and kaon decay data, including standard model interference in rare K to pi l+ l- modes.
-
Scalar leptoquark effects on $B \to \mu \bar\nu$ decay
A scalar leptoquark S1 near 1 TeV can raise B to mu nu to the Belle central value, but required Yukawa couplings are large and several LHC and EDM constraints already cut into that parameter space.
Discussion (0). Continue with ORCID to comment.