Project

General

Profile

Idea #6093

Document our recommendations for versioning of overlays, etc.

Added by Kurt Biery over 5 years ago. Updated almost 2 years ago.

Status:
Closed
Priority:
Normal
Assignee:
-
Category:
Under Consideration
Target version:
-
Start date:
05/01/2014
Due date:
% Done:

0%

Estimated time:
80.00 h
Experiment:
Duration:

Description

We expect that raw data formats can change over time, so we should develop, document, and possibly demonstrate a recommendation for the best way to do this in overlay classes.

We have an example of a way to do this in the NOvA DAQDataFormats package. I'm sure that there are other ideas and examples, also. I added a version number field to the LBNE 35-ton data classes that I wrote, but I didn't actually implement versioning.

If we decide that we want to demonstrate our preferred model, we could use the artdaq::Fragment class to do that.

History

#1 Updated by Eric Flumerfelt almost 3 years ago

  • Category set to Under Consideration
  • Target version deleted (577)

We could use a piece of the Fragment header for this, something that is set in the overlay's constructor...

#2 Updated by Eric Flumerfelt almost 2 years ago

  • Status changed from New to Closed

This has been implemented in artdaq_core for some time. Closing.



Also available in: Atom PDF