Can artdaq::Fragment have zero dependencies on other code in the art stack?
Recently, a couple of folks on protoDUNE wondered whether it might be possible to look at raw data files written by artdaq with bare ROOT tools. The stated purpose for this way of looking at raw data would be for quick debugging. It was suggested that having a way to build some fraction of the data-access classes outside of cetbuildtools might be helpful in this regard.
One first step in this direction would be to minimize the dependencies of artdaq::Fragment on other code in the artdaq/_art_ stack. This would probably entail moving it into a package that has very limited dependencies.
Ron may already be looking into this.
#2 Updated by Eric Flumerfelt about 3 years ago
- Category set to Under Consideration
- Target version deleted (
We're pretty sure at this point that there's minimal reduction possible here, as an "artdaq-data" product would still have to rely on cetlib (for BasicPlugin), and that drags boost along with it (which means that we would still be requiring 2/3 of the mass of the product stack (gcc comes, too)) to build the thing.
#3 Updated by Eric Flumerfelt about 3 years ago
- Status changed from New to Closed
- Target version set to artdaq v2_02_00
artdaq_core now depends on canvas, which is as low as we can practically go. If someone wants to deal with Fragments in an entirely binary fashion, then we should consider that issue separately. There also still remains the possibility of creating a version of BoardReader with minimal dependencies for running on embedded systems.