KM3NeT front-end and readout electronics system: hardware, firmware, and software

he KM3NeT research infrastructure being built at the bottom of the Mediterranean Sea will host water-Cherenkov telescopes for the detection of cosmic neutrinos. The neutrino telescopes will consist of large volume three-dimensional grids of optical modules to detect the Cherenkov light from charged particles produced by neutrino-induced interactions. Each optical module houses 31 3-in. photomultiplier tubes, instrumentation for calibration of the photomultiplier signal and positioning of the optical module, and all associated electronics boards. By design, the total electrical power consumption of an optical module has been capped at seven Watts. We present an overview of the front-end and readout electronics system inside the optical module, which has been designed for a 1-ns synchronization between the clocks of all optical modules in the grid during a life time of at least 20 years

Time series of oceanographic parameters measured at the Lacaze-Duthiers Canyon (LDC) and the open-sea convection region in the Gulf of Lion (LION) from January 2008 to June 2010.

<p>(<b>a</b>) Potential temperature at 500 and 1,000 m depth at the LDC mooring site and (<b>b</b>) from various water depths at the LION site, jointly with (<b>c</b>) salinity at 2,300 m depth, (<b>d</b>) horizontal current speed and (<b>e</b>) vertical current speed from various water depths at the LION site. The four levels of temperature measurements at LION presented here are a sub-set of measurement depths (see Fig. S1). Essentially stable temperatures in the deepest layers in 2008 show that open-sea convection reached only 700 m and did not modify the deep water in the study area. In contrast, strong convection events, reaching 2,300 m depth, occurred during February-March 2009 and 2010 with an abrupt cooling of the upper water column and an increase in temperature and salinity in the deep layers. A concurrent increase in current speed was also noticed in winter 2009 and 2010. The 5-month long data gap in 2009 is due to a damaging of the mooring line during the April 2009 recovery, which induced a postponement of its redeployment to September 2009.</p