Think about ways to support different configuration formats which still maintaining traceability and archiving
At protoDUNE, the Trigger Fragment Generator folks are storing a JSON string inside their FHiCL BoardReader configuration. Within their code, they are using the jsoncpp library to navigate through that JSON once they pull it out of the FHiCL.We should talk about ways to handle this sort of need.
- is there a FHiCL-to-JSON converted in the artdaq-database package?
- do we need to start including a JSON package in our software suite?