ProtoDUNE DAQ Topics

From DUNE
Jump to: navigation, search

Contents

Intro

This page is in early stages of development and is subject to frequent changes. Currently, most of the material here is transcribed from http://www-pnp.physics.ox.ac.uk/~barr/dune/. A few items on the bottom on the least are yet to be developed and are placeholders.

DAQ Topics

Physics Requirements capture

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).

Description

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).

Timeline

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.


Groups/people (tentative)

(B. Viren), (M. Potekhin), (T. Junk), (J.Nowak)

Simulation


Warm interface board

Note the warm interface board is currently discussed in both the electronics and the DAQ working groups. It will eventually end up in one of these. It is a critical interface from the point of view of reception of fast digital signals from the cold, detector grounding and noise reduction. It could be a critical interface for the DAQ depending on how much of the DAQ functionality goes on it (timing, backpressure, etc.). In the schedule, it is on the critical path for development for ProtoDUNE. At the CERN DAQ meeting, from the DAQ side, we decided to limit it to one of two choices (a) An SBND-like WIB (already in design at BNL) or (b) a lightweight WIB that passed most of the functionally responsibility on to the RCEs (under study at SLAC and UCDavis), with a choice between these two to be made soon. Any changes that the electronics group requires are still possible (but I don't think there are many). Because of the pressing need to get started, the interface from the WIB to the downstream FELIX DAQ was left for another time it may be able to utilize whichever of (a) or (b) gets picked, or it may need a respin of the board.

Description

The warm interface board plugs directly into the flange from the cryostat and contains the circuitry to talk with the cold boards inside.

Timeline

Urgent, it is desired to have working first prototypes ready by July 2016.

Groups/people (tentative)

BNL, BU, UCDavies, SLAC, others

Useful links

Try to get some links to slides from past talks by e.g. Jack Fried, Eric Hazen and e.g. Matt Graham talk March 21st Electronics meeting.

Timing

There is a first draft of timing design document to be updated soon.


TPC RCE system

Description

Use the COB/RCE platform for data buffering and processing. Form consortium of groups to realize the RCE DAQ system (Likely SLAC, UC Davis, Oxford, RAL). Finish discussions and decisions on WIB. Define new RTM and confirm schedule for design and constructing it

Timeline

We aimed for a first draft of proposal today, but due to illness, it will follow very soon. Must plan to reestablish a vertical slice test once the 35t is over. Version of the hardware must be available at same time as WIB development (Summer 2016). Sufficient electronics to read out one APA ready by January 2017.

Groups/people (tentative)

TBD

Useful links

Matt Graham's talk March 7th DAQ meeting. CD1-refresh documentation. Others?


TPC readout - FELIX system

Description

Alternative readout mechanism, using FELIX interface and computers as a data pipe.

Timeline

Possible to readout some of APAs with FELIX on day one, but also possible to read everything with RCEs on day-one with FELIX readout working later in ProtoDUNE program.

Groups/people (tentative)

(Karol Hennessey), (Eric Church), (Giovanna Lehmann)

Useful links

Karol/Eric's talk March 21st DAQ meeting, Giovanna's talk in November


Photon detector SSPs (DAQ interface part)

The main discussion on the SSPs is in the PD group.

Description

The SSP design will only marginally change compared with the 35t from the DAQ end. When the physics requirements capture for ProtoDUNE is done, and we understand the rates better, we must check we have a proper plan for handling the data volume from the SSPs, and that they can fit in with the triggering schemes devised for ProtoDUNE (probably the answer is yes).

Timeline

Need understanding of channel counts, data rates and data handling strategy very soon. Discussion in PD group (including Martin and Argonne) on lessons learned from 35t and further improvements and features. Write sub-section of design report for DAQ section. Following design review is a VST test needed to verify timing system and to validate improvements from 35t (answer yes). Test interface with new timing system. Other VSTs?

Groups/people (tentative)

TBD

Useful links

SSP manual on docdb. Others (e.g. is there a more general description of PD system in CDR?)


artDAQ

DAQ toolkit used as the foundation of the DUNE DAQ

Description

TBD

Timeline

Plan upgrade to DAQ for ProtoDUNE, start defining this as soon as the 35t run is finished.

Groups/people (tentative)

UK groups working on Board-Reader software to interface our hardware with artDAQ. UK groups involved in software trigger processing. Fermilab group heavily involved in 35t DAQ. More help needed for ProtoDUNE. Fermilab+UKgroups+SLAC involved in realizing DUNE triggering and readout architecture (see CD1-refresh docs). Needs more physicist effort to help develop new features.

Useful links

Point at redmine site and some more didactic material

Backpressure and run start mechanism task force

Description

Discussions needed (very fast if this impacts the timing system).

Timeline

TBD

Groups/people (tentative)

This will be a short-term process, but with someone able to check the bits that get constructed don't encounter difficulties implementing once it gets under way.

Useful links

TBD

Slow Control

Description

There are two aspects to slow control (a) Safety and control and (b) Monitoring of DAQ quantities. The choice for (a) and possibly part/all of (b) is the SCALA (formally called PVSS) system, which is the CERN standard.

Timeline

The first step is to start assembling the team. In parallel with forming the team, we will start to come up with the list of things we need to control and monitor. We should split the aspects that deal with the safety of the experiment (different resilience and redundancy standards to apply) from the control and monitoring of the detector and from the DAQ configuration of the detector (this last part may be dealt with separately, see the User interface and DB section). When we have the beginnings of a list, we will start to write down the requirements. As the team forms, we will revisit the lists and requirements. It will be very helpful to have both people willing to be leaders of this work, and also people willing to take on a small component of it.

Groups/people (tentative)

TBD

Useful links

UI, DB and DB interface to offline

(Note this is what we have been calling "Run Control" in LBNE, but I have tried to avoid that term, because we have separated out the monitoring and control of individual DAQ processes inside artDAQ to the artDAQ section of these web pages (for now)).

Description

The user interface is a mainly web-based control program, that allows the runs to be started and stopped, configuration changes to be made, and monitoring information (on the DAQ and the slow controls to be viewed). The aim is to have a one-stop portal to the whole detector to facilitate remote access for shift taking, expert intervention and general status information on the experiment. This has the advantage that access conrol (passwords etc.) can be done in one place, and can allow the system to prevent multiple people from having control at the same time (avoid them changing in a bad combination). Behind the scenes, the user interface is using a database driven web content management system, incuding the database tables with historical run information, configuration settings and DAQ/slow control monitoring variables. This group is also responsible for transfering the history information in these databases into the databases needed for the offline.

Timeline

While we are busy setting up other groups, this one could (if needed) take a pause for a few weeks still. After that, we need to start with requirements for the User Interface for protoDUNE, and also look at possible synergy between the single and dual phase parts of ProtoDUNE.

Groups/people (tentative)

TBD

Useful links

Add Erik B's demo link + any info on IceCUBE run control interface. Add Django links


Offline interface for data, data staging at experiment, online processing farm

Description

TBD

Timeline

TBD

Groups/people (tentative)

TBD

Useful links

TBD


Trigger counter and beam timing inputs

Description

TBD

Timeline

TBD

Groups/people (tentative)

TBD

Useful links

TBD


Beam position monitor input

Description

TBD

Timeline

TBD

Groups/people (tentative)

TBD

Useful links

TBD

CERN APA tests

Description

TBD

Timeline

TBD

Groups/people (tentative)

TBD

Useful links

TBD


Installation at CERN

Description

TBD

Timeline

TBD

Groups/people (tentative)

TBD

Useful links

TBD

Commissioning at CERN

Description

TBD

Timeline

TBD

Groups/people (tentative)

TBD

Useful links

TBD


DAQ support for running at CERN

Description

TBD

Timeline

TBD

Groups/people (tentative)

TBD

Useful links

TBD


TITLE

Description

TBD

Timeline

TBD

Groups/people (tentative)

TBD

Useful links

TBD