July 2014 work items » History » Version 4
Kurt Biery, 07/16/2014 03:05 PM
h1. 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:
# 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?
# 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?
# Tag and release the current _mu2e-artdaq_ code [Ron]
# Update the _mu2e-artdaq_ code to use the latest version of _artdaq_ [Ron]
# 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_
** [Kurt] my understanding is that this will proceed in the background as time permits
# 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]
# Develop the firmware to transfer data over the optical fiber to a real or simulated ROC. A first step in this may be to get this working in loop-back mode. (did I get this right?) [Rick]
# Tracker ROC work. This is outside the scope of the TDAQ subproject and should be paid for with Tracker funds. [Greg]
Coordination (management) tasks:
# 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]
# 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]
# Meet with Cosmic Ray Veto folks to further understand the needs of the CRV detector in terms of readout, triggering, and software filters. [Mark, Kurt, Ryan]
# Based on the discussion with CRV folks and others, document typical data taking and readout scenarios including sample data blocks at various points in the DAQ system, a description of how data blocks are uniquely identified and grouped together into "events", and the sequence of steps that are needed to select and write different types of "events" to disk. (Also, define what is meant by "event" in various contexts.) [TBD]
# Install EPICS and CSS on a Mu2e computer and document the steps that are needed to install, configure, control, and monitor typical slow controls entities. (did I get this right?) [Summer student]
Data processing tasks:
# [under consideration] Contribute to the _art_ modifications that will improve its abilities in an online context. [TBD]
Goals in the BOE documents: