Idea #21923: With a few code changes, we could support multiple logger processes sending events to the Dispatcher
Please add artdaq_daqinterface support for book-keeping firstLoggerRank
As described in the parent of this Issue, we can support multiple logger processes sending events to the Dispatcher if we make the logger art configurations identical. To help do that, it would be useful to have a "firstLoggerRank" parameter in the logger (DL or EB) FHiCL that indicates the lowest rank of the logger processes, and it would be best if that parameter is book-kept by DAQInterface so that its value is reliably filled.
A second request in this area is to have the option to turn off the addition of the "_dl<N>" suffix in the raw data file names. (I believe that John already has this second part implemented.)
JCF: satisying Issue #22129, if the FHiCL document of a logger process contains a firstLoggerRank parameter, set that parameter to be the lowest rank of any of the logger processes in the run
JCF: bump product_deps to v3_00_06o, designed to satisfy FNAL Redmine Issue #22129
#1 Updated by John Freeman 12 months ago
- % Done changed from 0 to 50
- Status changed from Assigned to Work in progress
DAQInterface release v3_00_06o is now available on the protoDUNE cluster, though it's not the default version used by JCOP (i.e., on np04-srv-024, you'd need to edit /nfs/sw/artdaq/DAQInterface/source_me<partition number> to use this version on partition <partition number>). As compared to v3_00_06n, v3_00_06o allows for the user to set "
disable_unique_rootfile_labels: true" in /nfs/sw/artdaq/DAQInterface/.settings (or whatever file you point the DAQINTERFACE_SETTINGS environment variable to); while this feature has been available on the "generic" DAQInterface whose releases are cut off the develop branch for several months now, this is the first time it's been introduced to the protoDUNE variant of DAQInterface. Also as compared to v3_00_06n, v3_00_06o will, if it finds the firstLoggerRank parameter in a logger process's FHiCL document, assign it the value of the lowest-ranked logger process in the run.
Still to be done is the implementation of the firstLoggerRank functionality for DAQInterface on its develop branch.
#2 Updated by John Freeman 12 months ago
- % Done changed from 50 to 100
- Status changed from Work in progress to Resolved
Now with commit 05bb5ee83f56a7c40da0ac1086eb820be8781cc0 on DAQInterface's feature/issue22129_bookkeep_firstLoggerRank branch, "standard" DAQInterface's behavior will be the same as protoDUNE-specific DAQInterface v3_00_06o described above vis-a-vis the firstLoggerRank parameter.
#4 Updated by John Freeman 11 months ago
That would happen if none of the artdaq processes wrote events to disk. This doesn't seem in and of itself a problem...is the idea that a configuration which contains firstLoggerRank but doesn't write data to disk would suffer from "code smell", and DAQInterface should warn people if it sees this?