40 likes | 153 Views
This proposal outlines the establishment of a real-time online event display system for local and remote use, designed to showcase 3D hits from muon detection and cosmic ray events. Utilizing existing software, the display aims to provide instant visibility into recorded events for verification and outreach purposes, impressing potential students and enhancing public engagement. The architecture features a local OEDServer that processes events and sends compact data to multiple OEDDisplays, ensuring minimal network traffic while maintaining fast performance to keep pace with high event rates.
E N D
Time: 08:11:12 Run: 18012 Snarl: 36871 ID: Multiple Muon Online Event Display ? • Propose setting up a Real-TimeONLINE Event Display • for local and remote use. • Fairly basic display of 3D (i.e. DeMuxed) hits • Based on existing ONLINE and OFFLINE software Mark Thomson, Cambridge
Motivation and Functionality Motivation • For remote control room : see the events as they are • recorded - verification that all is well (or not) • Outreach : seeing the events as they are recorded always • impresses the public/potential new grad. students • Publicity : good for talks/lectures if one can show the • detector in action Functionality • Fairly basic display : {UZ, VZ and XY} • + some history : able to recall last cosmic, multiple-muon, • neutrino candidate • Non-interactive : not meant to compete with the OFFLINE • event display • + MUST BE FAST to keep up with event rate Mark Thomson, Cambridge
LOCAL (e.g. SOUDAN, FNAL) Dispatcher OEDServer Remote sites OEDDisplay OEDDisplay OEDDisplay Possible Architecture • OEDServer runs locally – processes event and produces 3Dhits • OEDDisplays connect via TCP/IP Sockets • OEDServer sends compacted DeMuxed UVZQ hit list – minimal • network traffic ~ 1kbyte/second • - no sending of windows across network ! • OEDDisplays would display hits using ROOT based GUI • Multiple displays can connect to single server Mark Thomson, Cambridge
Work Required OEDServer • Set up a dispatcher client – probably running on • its own PC • Re-use rcServer Socket Communications code • DeMuxing : use AltDeMux (100ms/cosmic) • - easily sufficient to keep up with FARDET data • Produce 3D hits – code already used in AltDeMux OEDDisplay • Re-use rcGui comms and basic environment • Implement basic display • - code already in hand Require little new code ! If Desired, could be put together fairly rapidly Mark Thomson, Cambridge