Abstract

The Belle II experiment at KEK observed its first collisions in the summer of 2018. Processing the large amounts of data that will be produced requires conditions data to be readily available to systems worldwide in a fast and efficient manner that is straightforward for both the user and maintainer. This was accomplished by relying on industrystandard tools and methods: the conditions database is built as an HTTP REST service using tools such as Swagger for the API interface development, Payara for the Java EE application server, and Squid for the caching proxy. This article presents the design of the Belle II conditions database production environment as well as details about the capabilities and performance during both Monte Carlo campaigns and data reprocessing.

Highlights

  • The Belle II experiment at KEK observed its first collisions in the summer of 2018

  • It is the successor to the highly-successful Belle experiment, which provided the experimental foundation for the 2008 Nobel Prize in Physics in CP violation [1]

  • User access to the Belle II database is through a REST API, meaning that all accesses take the form of HTTP requests

Read more

Summary

The Belle II Experiment

The Belle II experiment is part of a broad-based search for new physics in the Intensity Frontier, focused on precisely measuring and comparing with theory branching fractions, angular distributions, CP asymmetries, forward-backward asymmetries, and a host of other observables. It is the successor to the highly-successful Belle experiment, which provided the experimental foundation for the 2008 Nobel Prize in Physics in CP violation [1]. The SuperKEKB accelerator upgrade will provide asymmetric electron-positron beams tuned to produce large quantities of B/anti-B meson pairs at 40x the instantaneous luminosity of KEKB and 50x the data taken with Belle. The primary purpose of the conditions database is to support data processing across the international Belle II computing grid, shown as the WAN connection at lower left that connects to the KEK computing center and Tier 1 computing centers, as well as interactive users. This is done offline, but is envisioned to become significantly more automated as Belle II matures

Belle II Database Software Architecture
Service Layers
Belle II Database Server Architecture
Client Interfaces
Database Performance
Upcoming Development
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.