...
This SpinQuest data management plan details the collaborations plan to responsibly manage the scientific data recorded by the SpinQuest experiment. This document sets lays out the SpinQuest collaboration plan of for the experimental facility at Fermilab NM4 and is intended as a reference for the plans of the upcoming experiment (E1039) using the SpinQuest target and detectors. The Collaboration Chair and Spokespersons Dustin and Spokesperson Dustin Keller (UVA) manages collaboration membership with Spokesperson with the help of the SpinQuest Institutional Board and fellow Spokesperson Kun Liu (LANL). The Fermilab liaison manages safety and experimental hall activities. Fermilab badge and ID manages computing accounts. The collaboration is responsible for the software utilities used for reconstruction, calibration and monitoring and all major aspects of event reconstruction.
Responsibilities
With the assistance of Fermilab IT the SpinQuest Collaboration is responsible for the data management at the NM4 facility including all target, spectrometer and physics data. The maintenance of this document, the plan that it describes and its implementation are the responsibility of the Software Management team of SpinQuest formed by project leadership. This team is made up of the University of Virginia and Los Alamos National Labs as well as additional institutions that volunteer to take ongoing roles in this regard.
...
The Fermilab E-1039/SpinQuest experiment is expecting to collect approximately 20 Tb of raw data between commissioning and the end of data acquisition in 20222024. The raw data is subsequently processed and stored in a MySQL database. The MySQL database will be approximately twice the size of the raw data. In addition, there is a substantial volume of simulated, Monte Carlo events produced and stored at collaborating institutions and universities.
...
The raw data are then decoded and stored in a MySQL database. The decoding takes the information in the raw CODA data records and translates them into a more user-friendly format, for example, assigning specific wires numbers in tracking chambers to digitized drift time information or hodoscope numbers to hits. Further processing then occurs on these data to change the hits into reconstructed tracks and events that are also stored in the MySQL database. The MySQL database is also hosted on site in the SpinQuest counting house. For ease of access and data security, the MySQL database is mirrored off site at the University of Virginia and separately at the University of Illinois and on a RAID system, and possibly other collaboration sites in the future..
It is the SpinQuest Collaboration’s policy that these raw data and processed MySQL data are available to collaboration members for use in collaboration-approved scientific studies and analyses. Completed analyses will be submitted for publication and shared with outside researchers. SpinQuest will maintain the ability to access these data for a minimum of 7 years after the completion of the experiment.
...
Processed Data: Processed data is initially stored on disk and migrated to institutional storage as required. The raw data from the SpinQuest detector are stored on disk, at a rate of about 0.05 TB/week, with information on the particles as they transverse the detector components as well as information on target polarization and target parameters. The processed data are also stored on disk for analysis by members of the SpinQuest research community to analyze. Processed data is in Data Stitch Tajima ( DST ) format which will be analyzed with a ROOT based reconstruction and analysis framework.
Run Conditions: Run conditions (machine energy, beam intensity, target polarization, etc.) are stored in the experiment logbook and in a database called .
Databases: Database servers are managed by SpinQuest and regular snapshots of the database content are stored along with the tools and documentation required for their recovery.
...