Journal article
Particle identification at FCC-ee
- Abstract:
- The prospects are presented for precise measurements of the branching ratios of the purely leptonic $B^+_c → τ^+ν_τ$ and $B^+ → τ^+ν_τ$ decays at the Future Circular Collider (FCC). This work is focused on the hadronic $τ^+ → π^+π^+π^− \bar{ν}_τ$ decay in both $B^+_c → τ^+ν_τ$ and $B^+ →τ^+ν_τ$ processes. Events are selected with two Boosted Decision Tree algorithms to optimise the separation between the two signal processes as well as the generic hadronic $Z$ decay backgrounds. The range of the expected precision for both signals are evaluated in different scenarios of non-ideal background modelling. This paper demonstrates, for the first time, that the $B^+ → τ^+ν_τ$ decay can be well separated from both $B^+_c → τ^+ν_τ$ and generic $Z → b \bar{b}$ processes in the FCC-ee collision environment and proposes the corresponding branching ratio measurement as a novel way to determine the CKM matrix element $|V_{ub}|$. The theoretical impacts of both $B^+ → τ^+ν_τ$ and $B^+_c → τ^+ν_τ$ measurements on New Physics cases are discussed for interpretations in the generic Two-Higgs-doublet model and leptoquark models
- Publication status:
- Published
- Peer review status:
- Peer reviewed
Actions
Access Document
- Files:
-
-
(Preview, Version of record, pdf, 881.6KB, Terms of use)
-
- Publisher copy:
- 10.1140/epjp/s13360-021-01810-4
Authors
- Publisher:
- Springer
- Journal:
- European Physical Journal Plus More from this journal
- Volume:
- 136
- Issue:
- 8
- Pages:
- 835
- Article number:
- 835
- Publication date:
- 2021-08-13
- DOI:
- EISSN:
-
2190-5444
- ISSN:
-
2190-5444
- Language:
-
English
- Keywords:
- Pubs id:
-
215247
- Local pid:
-
pubs:215247
- Source identifiers:
-
W3166955623
- Deposit date:
-
2026-02-12
- ARK identifier:
This ORA record was generated from metadata provided by an external service. It has not been edited by the ORA Team.
Terms of use
- Copyright date:
- 2021
- Licence:
- CC Attribution (CC BY)
If you are the owner of this record, you can report an update to it here: Report update to this record