1 / 9

Slice Test DAQ

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.

bella
Download Presentation

Slice Test DAQ

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. 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. Wilkinson P. Murray A. Tumanov Wilkinson, Tumanov Murray H. Stoeck Wilkinson Wilkinson, A. Drozdetski Murray

  2. Configuration Peripheral Crate FED Crate Local DAQ PC CFEB DAQMB CCB DDU CCB Write to BigPhys memory XDAQ I2O Event Builder Run Control PC Disk XDAQWIN ORCA readable

  3. Wrapping Event Builder Communications EmuFED • 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. GenericFED EmuConfigFED xdaqApplication EventReader EventWriter Event Builder

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

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

  6. FileReaderDDU HardwareDDU DDU DDUEventData CSCEventData ALCTData CFEBData CLCTData Interpreting the Data Format • 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

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

  8. 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 Crate VMEModule DAQMB CCB FakeCCB

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

More Related