1 / 15

Report on DAQ Workshop

MICE DAQ and Controls Workshop. Report on DAQ Workshop. Jean-Sebastien Graulich, Univ. Genève. Introduction Monitoring and Control Detector DAQ Conclusions and Afterthoughts. Introduction. Took place at Daresbury, Aug 31 – Sept 1 14 people registered Workshop goals

samson
Download Presentation

Report on DAQ Workshop

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. MICE DAQ and Controls Workshop Report on DAQ Workshop Jean-Sebastien Graulich, Univ. Genève • Introduction • Monitoring and Control • Detector DAQ • Conclusions and Afterthoughts Jean-Sébastien Graulich

  2. Introduction • Took place at Daresbury, Aug 31 – Sept 1 • 14 people registered • Workshop goals • Overview MICE needs and main issues • Decide general orientations for • Control and Monitoring • Detector DAQ Jean-Sébastien Graulich

  3. On the Agenda • Talks on Control and Monitoring (CM) • Talks on Detector DAQ (DDAQ) • Talks on integration between CM and DDAQ Jean-Sébastien Graulich

  4. Workshop Goals (A. Bross) • Refine “Physics” parameter List • Further develop an understanding of the D/C/M needs for • Beam Line • Cooling Channel • Detectors • Produce Baseline Proposal for • DAQ Online System • Controls system • Monitoring system • Produce Outline for Comprehensive MICE D/C/M specification document • Start from MICE-NOTE-GEN-097 (Draft01/JSG) • Goal to have draft (0/1?) ready for collaboration meeting • GIVE SERIOUS CONSIDERATION TOEXISTING SYSTEMS/SOLUTIONS Jean-Sébastien Graulich

  5. Key issues • For CM • Safety • Guarantee the stability of • Beam line, including target system • RF system • Absorbers • For DDAQ • Guarantee stability of the DDAQ system (no data loss nor data taking time loss • Guarantee the data quality (integrity and relevance) Jean-Sébastien Graulich

  6. About CM • EPICS has been presented (Brian Martlew) • Experimental Physics and Industrial Control System • Software framework for control monitoring • Free, Open Source • Based on Channel Access protocol • Large user community in physics : • Advanced Photon Source (Argonne), PSI, DESY, LBL, LANL, Jefferson Lab, KEK B-Factory • Expertise available • Daresbury, D0 at FNAL • EPICS was found complying with MICE requirements Jean-Sébastien Graulich

  7. About DDAQ • Detector data Readout must be performed at the end of the spill • Data has to be buffered in the FEE • There is an ADC problem • Conversion time for conventional ADC does not allow 600 muons/1ms spill • Critical for EmCal • The Particle-trigger scheme is not well defined • Particle trigger = Digitisation trigger ≠ Readout trigger • Should be flexible (allow calibration, cosmic events, etc…) • Data Volume: • 25 kB/μ (2 kB/μ if zero suppression in the tracker) • ~10 MB/spill or 25 GB/run • ~ 60 TB/year (2500 runs) Jean-Sébastien Graulich

  8. DAQ Architecture Proposal Trigger distribution Tracker EmCal TOF VME Crates Trigger + Ckovs Optical link Linux PCs Ethernet GigaBit Switch Remote Storage Online Online Storage Event Builder Monitoring Run Control Jean-Sébastien Graulich

  9. DAQ Software • UNIDAQ has been presented (Makoto) • Would require to write an Event Builder • LHC DAQ software have been presented (Emilio) • CMS design is not importable • DATE from Alice has the following functionalities Jean-Sébastien Graulich

  10. List of DAQ functions • Run control (state machine) with GUI • Configure DAQ topology • Select trigger • Start/stop (by user or by DCS) • Communicate status to DCS • Partitioning. Its importance is never stressed enough. • Minimal set of hardware access libraries (VME, USB, S-LINK), and ready-to-use methods to initialize interfaces. • Data flow • Push (or pull …) data from FE to Storage via (one or more) layer of Event-Building • DAQ performance check with GUI • Data quality monitoring (or framework to do it) • GUI most likely external • Logging (DAQ-generated messages) with GUI to select/analyze logs Jean-Sébastien Graulich

  11. Emilio pointed out • Users are not experts: provide them the tools to work and to report problems effectively. • Flexible partitioning. • Event-building with accurate fragment alignment and validity checks, state reporting and reliability. • Redundancy / fault tolerance • A proper run-control with state-machine • And simplifying to the users the tasks of Partition, Configure, Trigger selection, Start, Stop • A good monitoring framework, with clear-cut separation between DAQ services and monitoring clients • Extensive and informative logging • GUIs Jean-Sébastien Graulich

  12. About CM <->DDAQ • Long discussion • Not finalised Jean-Sébastien Graulich

  13. Monitoring System Jean-Sébastien Graulich

  14. Slow Control Detector DAQ RF Phase About CM <->DDAQ MICE User Interface Run Control UI Monitoring Data Log Data Storage Environment MICE Beam Line MICE Cooling Channel MICE Detectors Jean-Sébastien Graulich

  15. Conclusions • Decisions • CM will be based on Epics • DAQ will be based on VME bus • We’ll PC under Linux Easier if all VME have the same interface • To be done • Specifications for DDAQ, including trigger system -> Choose the DAQ software • Finalise discussion on DDAQ/CM interconnection • Design an Ethernet Network Infrastructure • Start Testing Jean-Sébastien Graulich

More Related