Streaming Task Force remit

The task force should examine the needs and requirements of streaming at the trigger/DAQ level as well as in the stripping process. The information required to perform analysis for the stripping should be revisited and the consequences for the workflows and the information stored should be reported. The issue surrounding the archiving of selection and reconstruction and how to correlate them with the code version used should be addressed. Extensive use cases should be given to support chosen solutions.

Streams to T0

• How many for physics: 1, 4 (exclusive, D*. dimuon, inclusive), ...
• Preliminary understanding of level of overlap if number of streams exceed 1
• Role of "hot" stream of reconstructed events for physics monitoring
  • Consequences for start of processing of RAW data
• Calibration streams
  • Consequence for start of processing of RAW data
• Amount of data

Stripping

• How many streams?
• How to organise streams
• First thoughts on correlation matrix
• Preselection similarities
• Use of "calibration" streams

Stripping Procedure

• How best to store event selection info
  • Event header
  • Event tag collection
  • what information is necessary
• Output of stripping jobs
  • B & D candidates
  • Physics analysis requirements
• Process sequencing? e.g. DaVinci -> Brunel -> DaVinci ??
  • consequences of sequencing options on data output and workflows

Trigger & Stripping cuts

• How and where to store event selection cuts (for reconstruction, trigger and stripping)
  • Conditions DB vs CVS
• How to ensure consistency between code version & cuts used