Abstract

The choice by the KM3NeT Collaboration to use a relational database for storage and bookkeeping of detector construction data, calibration data and management data is based on the experience of the ANTARES Collaboration, but has a broader horizon. Currently, the core of the system is an Oracle Real Application Cluster installation hosted at the CCIN2P3 computing centre in Lyon, but a geographically distributed database network is foreseen. Database access is provided by an Application Web server that not only provides a graphical user interface, but also channels HTTP requests to SQL to optimally retrieve or insert data, potentially establishing a bridge towards Cloud or Grid computing models.

Highlights

  • KM3NeT is a future European deep sea research infrastructure that will host a distributed network of neutrino detectors forming a neutrino telescope with a total volume of several cubic kilometers at the bottom of the Mediterranean Sea [1]

  • The choice by the KM3NeT Collaboration to use a relational database for storage and bookkeeping of detector construction data, calibration data and management data is based on the experience of the ANTARES Collaboration, but has a broader horizon

  • The KM3NeT neutrino telescope consists of an array of thousands of optical sensors built to detect the faint light in the deep sea from charged particles originating from interactions of cosmic neutrinos and the Earth

Read more

Summary

DAQ Events

An important requirement for the design of the KM3NeT database is the management of Collaboration membership and the roles of persons and institutions. The run number, the file size, the number of contained events, the run manager and the operational parameters are recorded. This is a relatively simple application of the database technology, it shows the feasibility of the database design in an operational mode. A local database cache, in the same subnet as the Run Control is used as a buffer for storage of communication data to improve fault tolerance. This cache is accessed via the HTTP protocol, both for reading and writing. In figure 2, the role of the database in the data flow of the Run Control is schematically shown

Trigger system
RELATIONAL DATABASE AS STORAGE SYSTEM
Internet read
Findings
CONCLUSIONS
Full Text
Paper version not known

Talk to us

Join us for a 30 min session where you can share your feedback and ask us any queries you have

Schedule a call

Disclaimer: All third-party content on this website/platform is and will remain the property of their respective owners and is provided on "as is" basis without any warranties, express or implied. Use of third-party content does not indicate any affiliation, sponsorship with or endorsement by them. Any references to third-party content is to identify the corresponding services and shall be considered fair use under The CopyrightLaw.