Handle run-based and spill-based data
In our discussions with Lariat, the subject of how to handle run-based and spill-based data came up. Basically, this would be information that is relevant for the whole run (or spill) and does not need to be repeated with each event, but would be valuable to have in the data file that is written by that DAQ.
Thinking about this a little bit, it seems like the right way to do this would be to pass this data to the art Run and Subrun data products.
The work involved in making this happen would include talking with art folks to determine if this approach makes sense, and if so, what would be the right way to do it in art. There could be some spin-offs of this task in the art project, if we determine that art changes are needed to support this.
The time frame for needing this will depend on how urgently the Lariat folks will need it. How quickly we can deliver it will depend on a number of things, including whether it could be supported within art and artdaq without substantial changes.
#4 Updated by Eric Flumerfelt about 2 years ago
- Status changed from New to Closed
I'm closing this issue because we have demonstrated methods for doing this (BuildInfo, configuration stored in data files). If there is a specific need that arises in the future, we can deal with it as a new issue (and hopefully resolve it faster than ~4 years).