9
Slice Test DAQ Wrapping Event Builder Communications Local File Writing File Input to Event Builder Interpreting the Binary Data Format ROOT Analysis Trigger Trackfinder Input and Output Event Builder Output Format Peripheral Crate Control Use Cases For Test Beam I. Suzuki, D. Charak, R. Wilkins P. Murray A. Tumanov Wilkinson, Tumanov Murray H. Stoeck Wilkinson Wilkinson, A. Drozdetski Murray

Slice Test DAQ

  • Upload
    bella

  • View
    32

  • Download
    0

Embed Size (px)

DESCRIPTION

Slice Test DAQ. Wrapping Event Builder Communications Local File Writing File Input to Event Builder Interpreting the Binary Data Format ROOT Analysis Trigger Trackfinder Input and Output Event Builder Output Format Peripheral Crate Control Use Cases For Test Beam. - PowerPoint PPT Presentation

Citation preview

Page 1: Slice Test DAQ

Slice Test DAQ

Wrapping Event Builder CommunicationsLocal File WritingFile Input to Event BuilderInterpreting the Binary Data FormatROOT AnalysisTrigger Trackfinder Input and OutputEvent Builder Output FormatPeripheral Crate ControlUse Cases For Test Beam

I. Suzuki, D. Charak, R. WilkinsonP. MurrayA. TumanovWilkinson, TumanovMurrayH. StoeckWilkinsonWilkinson, A. DrozdetskiMurray

Page 2: Slice Test DAQ

Configuration

DAQMBCCB

Local DAQ PCPeripheral Crate

Disk

Write toBigPhysmemory

CFEBDDUCCB

FED Crate

XDAQI2O

ORCAreadable

Event Builder

XDAQWIN

Run Control PC

Page 3: Slice Test DAQ

Wrapping Event Builder Communications

• Input and Output to Event Builder are defined by I2O messages

• We want to encapsulate the buffering and I2O packing, unpacking, and message handling into a common FED class, so each subdetector can share it.– Avoids much duplicated code– Lets us change things easily

• STATUS: Being tested– Triggering not clear– Chamber and trackfinder

events not one-to-one.

EventReader

EventWriter

EmuFED

GenericFED EmuConfigFED

xdaqApplication

Event Builder

Page 4: Slice Test DAQ

Local File Writing

• We need to write a stream of local data because:– Event rate very fast… not clear that the Event Builder

can handle it.

– Needs to be done for calibrations runs in the final system, anyway

• Status: Utilities written, but no XDAQ interface.

Page 5: Slice Test DAQ

File Input to the Event Builder

• We do want to be able to combine chamber and trigger trackfinder data offline.

• Working on XDAQ application to control this

Page 6: Slice Test DAQ

Interpreting the Data Format

HardwareDDU FileReaderDDU

DDU

DDUEventData

CSCEventData

CFEBData ALCTData CLCTData

• Rick: built C++ objects from the big multidimensional arrays that come from Jason Gilmore’s C unpacking routines– Only DDU, DAQ motherboard, and

cathode data, no LCT

• Alex: – Validation package– Organized data better– getting rid of the C vestiges.

• STATUS: Still need trigger motherboard data– Formats still stabilizing

Page 7: Slice Test DAQ

ROOT Analysis Objects

• Will be based as closely as possible on the classes from the data unpacking– Maybe even using those classes themselves

• Pat will take the ROOT classes at CERN June 3-5, so that will be a good time to get questions answered.

Page 8: Slice Test DAQ

Peripheral Crate Control Software• Based on Stan Durkin’s C++

prototype of tried-and-true C cfeb_control

• Re-engineered by Rick• Validated by Alexei

STATUS:• need to integrate recent

additions• Not tested with multiple crates

and chambers

DAQMB

VMEModule

Crate

CCB

FakeCCB

Page 9: Slice Test DAQ

Event Builder Output Format

• If we’re combining chamber and trackfinder data, we need a data format with things like event headers and readout headers

• Giacomo Bruno’s DaqPrototype package provides these, with the additional benefit of being ORCA-readable!

• STATUS: Being written