Plans for now: Go full speed on this. To bootstrap the discussion on the data taking requirements for protoDUNE, the DAQ group must provide example readout scenarios to the other groups for discussion and to wait for comments and alternative suggestions before finalizing the DAQ design. Given the milestone to have a design review by June/July, it is very important these discussions converge well before then. Discussions will take place in the following meetings: DAQ group, protoDUNE measurement group, photon detector group and software and computing group (list other groups).
Make a list of requirements for (a) the ProtoDUNE DAQ and (b) the DUNE FD DAQ. This includes the triggering, considerations for handling the data. It couples strongly into the activities of the offline and computing groups and should be done alongside them. Various options for including alternative strategies in the case that one of the upstream components fails to meet the assumptions such as noise levels or faulty ADC codes (e.g. alternatives could be compressing at a different point in the architecture, or reducing the rate of events that can be delivered).
This work should be done as soon as possible. Optimizations on the design depend on it. This includes estimating the computing requirements for the ProtoDUNE. For the far detector, it includes firming up the estimates we made for CD3A on underground power, computing room space underground and on the surface and network infrastructure. It is already difficult to change these things but will be harder the later we are.
(B. Viren), (M. Potekhin), (T. Junk), (J.Nowak)
[Anything from Brett/Maxim et al that it is helpful for people to see yet?]
We don't have a wiki website that has authoristion for lots of users yet, so we are using the following shared google-docs page (add once we are on sharepoint and have a password for this page. We want to hear your comments of fixes/additiomns to this page. For now, please E-mail them to Giles, sorry this is not very good.