The Event as an Object-Relational Database: Avoiding the Dependency Nightmare
C. D. Jones

TL;DR
This paper proposes treating events as object-relational databases to reduce dependencies and improve flexibility in high-energy physics data management.
Contribution
It introduces a novel approach of modeling events as object-relational databases, including the use of a separate Association class for references.
Findings
Reduced dependency issues in data object references
Enhanced flexibility with multiple data sources for events
Improved system robustness and maintainability
Abstract
With the use of object-oriented languages for HEP, many experiments have designed their data objects to contain direct references to other objects in the event (e.g., tracks and electromagnetic showers have references to each other to denote matches). Unfortunately this creates tremendous dependencies between packages which lead to brittle development systems (e.g., if the electromagnetic code has a problem you may not be able to compile the tracking code) and makes the storage system more complex. We discuss how the CLEO III experiment avoided these problems by treating an event as an object-relational database. The discussion will include: the constraints we placed on our objects; our use of a separate Association class to deal with inter-object references; and our ability to use multiple sources to supply different data items for one event.
Peer Reviews
No public reviews on file for this paper yet. If you reviewed it on a platform where reviews are public (OpenReview, ICLR, NeurIPS, ICML), you can paste yours below so the community can read it here.
Videos
No videos yet. Explain this paper in a talk, walkthrough, or lecture? Add one.
Taxonomy
TopicsAdvanced Database Systems and Queries
