REVIEW 1 cited by
$h,Z\to \ell_i \bar\ell_j$, $\Delta a_{\mu}$, $\tau\to (3\mu,\mu \gamma)$ in generic two-Higgs-doublet models
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
Inspired by a significance of $2.4\sigma$ in $h\to \mu \tau$ decay observed by CMS at $\sqrt{s} = 8$ TeV, we investigate the Higgs lepton flavor violating effects in the generic two-Higgs-doublet model (GTHDM), where the lepton flavor changing neutral currents are induced at tree level and arisen from Yukawa sector. We revisit the constraints for GTHDM by considering theoretical requirements, precision measurements of $\delta \rho$ and oblique parameters $S$, $T$, $U$ and Higgs measurements. The bounds from Higgs data now play the major role. With the values of parameters that simultaneously satisfy the Higgs bounds and the excess of Higgs coupling to $\mu$-$\tau$ at CMS, we find that the tree-level $\tau\to 3\mu$ and loop-induced $\tau\to \mu \gamma$ could be consistent with current experimental upper limits; the discrepancy in muon $g-2$ between experiment and standard model prediction could be solved; and an interesting relation between muon $g-2$ and branching ratio (BR) for $\mu\to e \gamma$ is found. The GTHM results that the ratio $BR(h\to e\tau)/BR(h\to \mu \tau)$ should be smaller than $10^{-4}$ in order of magnitude. Additionally, we also study the rare decay $Z\to \mu \tau$ and get $BR(Z\to \mu\tau)< 10^{-6}$.
Forward citations
Cited by 1 Pith paper
-
Higgs lepton flavor violating decays in Two Higgs Doublet Models
A mini-review explaining that the type-III two Higgs doublet model can produce h to tau mu branching ratios near the present CMS bound while remaining compatible with tau to mu gamma and related flavor constraints.
Discussion (0). Continue with ORCID to comment.