July 2014 work items » History » Version 3

« Previous - Version 3/8 (diff) - Next » - Current version
Kurt Biery, 07/16/2014 02:35 PM

July 2014 work items

These are some notes on the tasks that were discussed at the 15-Jul-2014 Mu2e DAQ meeting [notes initially written by Kurt, additions/corrections welcome].

Planned or desirable deliverables:
  1. By June 2015, have the 6-server pilot system up and running. This includes the following functionality:
    • one DTC per server
    • at least one artdaq EventBuilder process running on each server
    • how many real or simulated ROCs per DTC?
    • what data rates should be supported? Between ROCs and DTCs? Between DTCs and EventBuilders? To disk?
  2. By an undetermined date, be able to provide single-server test systems to subdetector groups for ROC development and testing or detector development and testing. Providing such a system does not necessarily imply buying or donating a computer or other hardware. Instead, the DAQ group could provide recommendations on the appropriate server(s), PCIe card(s), network switch(es), etc. that the subdetector group should purchase. It does imply providing the firmware and software that would be run to acquire and store the data. This could take the form of a set of instructions for fetching, installing, building, and running the software, or the DAQ group could choose to assist with some of those steps. The features that would be part of such a system would be the following:
    • how would configuration be handled?
    • what level of online monitoring would be included?
Software tasks:
  1. Tag and release the current mu2e-artdaq code [Ron]
  2. Update the mu2e-artdaq code to use the latest version of artdaq [Ron]
  3. Split the mu2e-artdaq code into two packages, one with just the data format classes [Ron & Kurt]
    • the repository has already been created: mu2e-raw-data
  4. Investigate the use of JavaScript as a technology to use as part of providing tools in artdaq that facilitate debugging and testing hardware and firmware [Ron]
    • [Kurt] my understanding is that this will proceed in the background as time permits
  5. Develop a set of C++ classes and FHICL configuration files that demonstrate the reading of individual fragments from hardware (e.g. a DTC or a DTC connected to a real or simulated ROC) or a file. [Ron]
Coordination (management) tasks:
  1. Meet with Rob K. and possibly others to further specify the plan for organizing Mu2e DAQ code, raw data classes, monitoring modules, and other code into packages (possibly separate git repositories and UPS products). Document the plan [Kurt]
  2. Meet with Rob K. and possibly others to further specify the plan for breaking data packets that are useful in the online (for efficient network transfers) into data objects that are desirable in the online and offline analysis modules (in art). Document the plan. [Kurt]
  3. Meet with Cosmic Ray Veto folks to further understand the needs of the CRV detector in terms of readout, triggering, and software filters.

Goals in the BOE documents: *