EPJ Web Conf.
Volume 212, 2019The 12th International Workshop on e+e- Collisions from Phi to Psi (PhiPsi 2019)
|Number of page(s)||8|
|Section||Status of Facilities and New Projects|
|Published online||17 June 2019|
MEG II and Mu3e status and plan
INFN Pavia, Via A. Bassi 6, 27100 Pavia, Italy
2 Physics Institute, Heidelberg University, Im Neuenheimer Feld 226, 69120 Heidelberg, Germany
* e-mail: firstname.lastname@example.org
Published online: 17 June 2019
The MEG experiment searching for lepton flavor violating muon decay, finished data taking successfully in 2013. The final sensitivity of the experiment was 5.3 × 10−13, and since the experiment did not find any signal, the upper limit of the branching ratio of the µ → e+γ was set to be 4.2 × 10−13 at 90% C.L.. The MEG II experiment will have a target sensitivity improved by an order of magnitude down to 6 ×10−14 with three years data taking. In 2018 after the detector integration, the muon beam data taking took place with a limited number of readout channels. In 2019, the engineering run and the physics run will be started. The Mu3e experiment will search for the lepton flavor violating decay µ+→ e+e−e+ with unprecedented sensitivity. Construction of the detector is going to start in 2020 and for the first phase a single event sensitivity of 2 × 10−15 is expected.
© The Authors, published by EDP Sciences, 2019
This is an open access article distributed under the terms of the Creative Commons Attribution License 4.0 (http://creativecommons.org/licenses/by/4.0), which permits unrestricted use, distribution, and reproduction in any medium, provided the original work is properly cited.
Current usage metrics show cumulative count of Article Views (full-text article views including HTML views, PDF and ePub downloads, according to the available data) and Abstracts Views on Vision4Press platform.
Data correspond to usage on the plateform after 2015. The current usage metrics is available 48-96 hours after online publication and is updated daily on week days.
Initial download of the metrics may take a while.