1 / 17

L3 DAQ the past, the present, and your future

Explore the evolution of the L3 DAQ system from the past to the future, detailing key components, operations, and upcoming changes. Learn about the Transition System Supervisor, communication flow, and interim solutions for smoother transitions. Stay informed on system updates and expert contacts.

osherer
Download Presentation

L3 DAQ the past, the present, and your future

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. L3 DAQthe past, the present, and your future Doug Chapin for the L3DAQ group DAQ Shifters Meeting 26 Mar 2002

  2. The (soon to be) Past System Supervisor CPU COOR custom fiber ethernet future bus ROC VBD VRC CPU DAQ node Farm CPU VBDi SB ROC VBD VRC CPU DAQ node Farm CPU VBDi SB/ETG ROC VBD 4 VRCs 11 DAQ nodes 48 farm nodes ROC VBD trigger disable TFW info

  3. The Future System Supervisor CPU COOR All ethernet, except for TFW communication ROC SBC CISCO 6509 Switch ROC SBC Farm CPU ROC SBC Farm CPU Routing Master CPU TFW info ROC SBC trigger disable 48 farm nodes

  4. SBCs • SBC (Single Board Computer) • Intel ~1GHz, VME, dual 100Mb ethernet, 64MB flash for storage • “Dumb” Operation • No communication with supervisor • All farm nodes connect to each SBC • Receive routing information from RM • Pull event fragment over VME • place in memory buffer • send to appropriate node when routing info arrives

  5. A ReadOutCrate with SBC SBC VME J1 & J2 Slave Ready J3 Done

  6. Farm Nodes • Runs EVB/IO and Filtershell processes • Filtershell • This is ScriptRunner (L3 filters) • Recieves trigger programming info from supervisor • Recieves full event from EVB process • Event Builder (EVB) Operation • Each farm node connects to all SBCs • Receive crate list by event# from RM • Sends no. of free buffers to RM (“node ready”) • Builds full event from received fragments • No communication with supervisor

  7. Routing Master (RM) • Recieves “run” information from supervisor • Farm node list and crate list per bit • Gets bit fired by event# from TFW • Recieves no. of free buffers from each farm node • Decides which nodes receive which events • Sends routing info by event# to SBCs • Sends crate list by event# to farm nodes • Disables triggers when necessary

  8. Communication Flow Supervisor COOR Run information: crate and node list by trigger bit ScriptRunnertriggerprogramming Virtual SBC Routing info: destinationfarmnodeby event Crate listby event Routing Master EVB Filter-shell ROC SBC “node ready” Farm node Bits firedby event TFW info trigger disable

  9. Before the Future Begins • Issues • SBC delivery/installation will be steady but slow • Several months • RM, SBC, EVB, and Supervisor software need real DAQshifter-level abuse • Solution • Transitional SBC + VRC system

  10. The Transition System Supervisor CPU COOR VRC CPU ROC VBD VirtualSBC VBDi CISCO 6509 Switch ROC VBD Farm CPU VirtualSBC ROC SBC Farm CPU Routing Master CPU TFW info ROC SBC trigger disable 48 farm nodes

  11. Transition System Status • Super, RM, EVB, SBC all tested • They even work • Use of the system is imminent • Minor Issues / Big Changes • New monitoring • Control (“Reset L3”) • Trigger Disable!!! • Experts

  12. L3 Trigger Crate • TFW provides (ECL lines) • Ouput from L3DAQ • 128 “disable” lines, one for each trigger bit • Can now only disable 32 bits for lack of hardware!!! • Input to L3DAQ • 16 bit L3 transfer number (event number) • 128 bit “L1/L2 AND terms” (which bits fired) • Under development • “L3 Trigger Crate” to house the RM and receive/control TFW ECL lines • May take several months to complete

  13. L3 Disable: Interim Solution • Put RM on the TFW readout crate SBC • Spy on the TFW data block • Extract L1 fired bits and L3 transfer number • When L3-disable is needed • RM tells SBC to stop reading out the TFW crate • TFW crate goes front-end-busy and stops triggers • Acts as global disable • Sets a flag in the RM monitoring information • Cons • The actual L3 Disable line is not used • Shifter must check L3DAQ monitoring every time TFW crate is 100% front-end-busy • All L2 decisions are ignored!

  14. Control • COOR <-> Supervisor communication unchanged • Reseting L3 will be uncentralized • Farm node processes • online script “l3xreset”? • SBC and RM processes • online script “l3xdaq_reset”? • Supervisor and VRCs (virtual SBCs) • via the familiar “Farm Control” webpage

  15. L3 DAQ Experts • New expert contact list for L3DAQ • Our expertise does not overlap yet • At first • Andy (RM, SBC software) • Doug (VRCs, SBC hardware) • Ron (SBC hardware) • Gustaaf (EVB, Filtershell) • Others will join • Reiner? Martijn? Gordon (Supervisor)?

  16. Monitoring • All processes (SBC, RM, super, EVB) produce monitoring info • EVB and Filtershell use seperate monitor server • Two new monitor clients • jMon will be deprecated • l3xmon • EVB and Filtershell info • üMon is the client of the future • SBC, RM, and Supervisor info currently • EVB info (missing crates!) added in future • Send comments to sean@fnal.gov

  17. Summary • Transition system in place very soon • Bad news: • New problems, new monitoring, new experts, new instructions • Good news: • Known VRC problems still around • Additional fun, excitement, and adventure • Stay tuned to • d0daqshifters mailing list • http://d0onlinelx.fnal.gov/www/groups/l3daq/default.html

More Related