dorsal/arxiv
View SchemaA Relational Database Model for Managing Accelerator Control System Software At Jefferson Lab
| Authors | S. Schaffner, T. Larrieu |
|---|---|
| Categories | |
| ArXiv ID | physics/0111065 |
| URL | https://arxiv.org/abs/physics/0111065 |
| Journal | eConf C011127:WEAP074,2001 |
Abstract
The operations software group at the Thomas Jefferson National Accelerator Facility faces a number of challenges common to facilities managing a large body of software developed in-house. Developers include members of the software group, operators, hardware engineers and accelerator physicists. One management problem has been ensuring that all software has an identified maintainer who is still working at the lab. In some cases, locating source code for 'orphaned' software has also proven to be difficult. Other challenges include enforcing minimal standards for versioning and documentation, segregating test software from operational software, encouraging better code reuse, consolidating input/output file storage and management, and tracking software dependencies. This paper will describe a relational database model for tracking the information necessary to solve the problems above. The instantiation of that database model provides the foundation for various productivity- and consistency- enhancing tools for automated (or at least assisted) building, versioning, documenting and installation of software.
{
"annotation_id": "82698fc1-cca6-4c64-b23c-58ff994ec6d7",
"date_created": "2026-03-02T18:00:36.105000Z",
"date_modified": "2026-03-02T18:00:36.105000Z",
"file_hash": "85d2c9965bddfb4572e612c293c295f2f55af52a0a308d45fae109cc60824f7d",
"private": false,
"record": {
"abstract": "The operations software group at the Thomas Jefferson National Accelerator\nFacility faces a number of challenges common to facilities managing a large\nbody of software developed in-house. Developers include members of the software\ngroup, operators, hardware engineers and accelerator physicists. One management\nproblem has been ensuring that all software has an identified maintainer who is\nstill working at the lab. In some cases, locating source code for \u0027orphaned\u0027\nsoftware has also proven to be difficult. Other challenges include enforcing\nminimal standards for versioning and documentation, segregating test software\nfrom operational software, encouraging better code reuse, consolidating\ninput/output file storage and management, and tracking software dependencies.\nThis paper will describe a relational database model for tracking the\ninformation necessary to solve the problems above. The instantiation of that\ndatabase model provides the foundation for various productivity- and\nconsistency- enhancing tools for automated (or at least assisted) building,\nversioning, documenting and installation of software.",
"arxiv_id": "physics/0111065",
"authors": [
"S. Schaffner",
"T. Larrieu"
],
"categories": [
"physics.acc-ph"
],
"journal_ref": "eConf C011127:WEAP074,2001",
"title": "A Relational Database Model for Managing Accelerator Control System Software At Jefferson Lab",
"url": "https://arxiv.org/abs/physics/0111065"
},
"schema_id": "dorsal/arxiv",
"source": {
"execution_id": "77ee83d4-9196-4405-a34e-b46fca12b117",
"id": "arXiv Dataset IDs",
"type": "Model",
"variant": "snapshot-2026-03-01",
"version": "0.1.0"
},
"user_id": 1000002
}