1 / 21

DAQ software for SND detector

DAQ software for SND detector. Budker Institute of Nuclear Physics, Novosibirsk M. Achasov, A. Bogdanchikov, A. Kim, A. Korol. VEPP-2000 collider. In the past: SND @ VEPP-2M Years: 1995 - 2000 Energy (2E): 0 . 36 – 1 . 4 GeV. Today: SND @ VEPP-2000 Project started: 2000

silviaj
Download Presentation

DAQ software for SND detector

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. DAQ software for SND detector Budker Institute of Nuclear Physics, Novosibirsk M. Achasov, A. Bogdanchikov, A. Kim, A. Korol

  2. VEPP-2000 collider In the past: SND @ VEPP-2M Years: 1995 - 2000 Energy (2E): 0.36 – 1.4 GeV Today: SND @ VEPP-2000 Project started: 2000 Energy: 1.4 - 2 GeV Luminosity: 1032 (2 GeV) Perimeter: 24.4 m Collision time: 82 nsec Beam current: 0.2 A Bunch length: 3.3 cm Energy spread: 0.7 MeV Session 1, SND DAQ software

  3. VEPP-2000 collider Session 1, SND DAQ software

  4. SND DAQ requirements • Loose electronic selection conditions (FLT), strong software (TLT) filtration (ratio to 10%). • Readout process should work on the stand-alone equipment, separately from processes which consumea lot of computational power (TLT). • Event selection using fully reconstructed events – L3 farm. Session 1, SND DAQ software

  5. Main data flow 100 Hz 1 KB 1 kHz 4 KB 1 kHz 4 KB 1 kHz 1 KB Readout and events building Events packing Events filtering Storage Expected rates: • Events fragments: 4 МB/s are read fromIO processors over Ethernet; • Event building: 4 MB/s; • Event packing: 1 МB/s; • Events filtering (90% screening): 100 KB/sec. Session 1, SND DAQ software

  6. L3 Sum L3 Readout L3 Storage Raw events transfer (alternatives) L3 L3 Readout L3 Storage Session 1, SND DAQ software

  7. Raw events transfer (software layers) • Abstract layer • Container capture • Read events from container • Write events to container • System layer • Global File System (GFS) – tested • Shared raw disks • Network File System (NFS) • Hardware layer • Shared SCSI disk - tested • Network disk Session 1, SND DAQ software

  8. KLUKVA KLUKVA KLUKVA CAMAC KLUKVA CAMAC TLT computers DAQ architecture Detector Off-line Front-end electronics Filtered events Backup X 12 X 16 Visualization Readout & Event Building Buffer Database Calibration process System support Session 1, SND DAQ software

  9. Main online processes • Events treatment : • Readout & event building • Scalers (statistics from electronic subsystems) • L3 (packing, reconstruction, filtration, statistics) • Calibrationon events • Control : • Operator interface • Distributed processes management • Context recovery after process crash • Informer (message analyzer) • Electronics sub-system control Session 1, SND DAQ software

  10. Initialization Idle Monitoring Full stop Monitoring Start Reject Stop Configuration Stop Success Pause Readout Pause Readout Auto-start Readout process state machine • Note: error branches are not shown, all errors cause Idle state. Session 1, SND DAQ software

  11. Process B child Process starter service Database TLT1 Process A: 2 Process B: 1 Process C: 3 TLT2 Process A: 1 Process D: 3 Online Computer TLT1 Online Computer TLT2 Starter service Starter service Process A Process D Process A Process C Process A Process D Process A Process C OK, one session ID needs to stop Process C Process D needs to start Session 1, SND DAQ software

  12. Processes states and recovery • After start processes should receive domain name from “domain distributor server“ (DD). Each domain contains fixed name variable to store a path to recover program. When process crashes (tears connection), DD starts recover program with domain name as parameter. • Current process state data are stored in the OnlState database and may be accessed by other processes. • State variable type: int, float, string, arrays; access index: domain_name/variable_name • Atomic domain access. Session 1, SND DAQ software

  13. Domain request Free Busy Process finished Start recovery program Process crashed Context recovery Re-register domain Distributor server crashed and restarted Confirmation timeout Confirmation Process context recovery Domain states: Session 1, SND DAQ software

  14. Online Databases • Online state DB • Conditions DB • Configurations DB • Bookkeeping DB } Closely tiered. To simplify access integrated interface is supported. Implementation: RDBMS (MySQL) Session 1, SND DAQ software

  15. Configurations & Bookkeeping API Table description (SQL format) table.sql parser C++ description and implementation table.h table.cc Application Session 1, SND DAQ software

  16. Operator interface Run control Web-log Database access Process control Communication Personal settings Status Selective views Run conditions Occupied resources Users contacts User info Start Stop Pause Message search Configurations Processes start list Chat UI details Message add UI Calibrations UI colors Silence Extended messages E-mail notifications Statistics Scalers selection Session 1, SND DAQ software

  17. PHP scripts Online Process Configurations PHP API Configurations API Calibrations API Calibrations PHP API Online States PHP API Online States API Recovery API Recovery PHP API Web-log PHP API Web-log API Operator interface components HTTP server RDBMS HTML javascript Session 1, SND DAQ software

  18. Web-log messages The web-log toolkit consists of several interfaces written in languages PHP and C ++, which allow to choose, add and expect the message. Each message has attributes: • Alarm – is on when required to draw attention of the operator immediately. • Date and time of the message. • Topic of the message (what field it belongs to). • Severity of the message (fatal mistake, error, warning, info, debug, trace). • Sender: user, host, process name. • Subject – the summary of the message. This is a basic field. • Message attachments of any MIME-type. Full description of the problem, pictures, diagrams can be presented in the attachment. Attachment has attributes: name, size and inline. The attribute inline is a recommendation for browsers, whether to include attachment in the message directly or display just a link. Session 1, SND DAQ software

  19. Statistics view (example) Session 1, SND DAQ software

  20. Design • High level robustness: raw events deep buffering; • High quality of filtering: full events reconstruction before filtering; • Reuse of off-line framework software; • Relational databases to store experiment configurations, states, calibrations; • Operator interface: web technologies . Session 1, SND DAQ software

  21. Status • DAQ system software status: • Event transfer mechanism were tested on the maximum possiblerates; • The most important functionality were realized; • Advanced features were added; • 2003-2004: system were used to receive events from the drift chamber prototype. Session 1, SND DAQ software

More Related