1 / 14

DAQ & Online

DAQ & Online. Definition of real-time processes in the farm Online calibration manage Insert of T3filter DAQ real run with t3filter. Definition of real-time processes in the farm.

jasper
Télécharger la présentation

DAQ & Online

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 & Online • Definition of real-time processes in the farm • Online calibration manage • Insert of T3filter • DAQ real run with t3filter W. Mei for DAQ & Online

  2. Definition of real-time processes in the farm • reduce stack size to lock the processes in physical memory and always keep higher priority than usual processes. • farm receiver, farm builder and T3filter are real-time processes now. (recompile must be executed in KRUNC. -rwxrwx--x -> -rwsrws--- ) W. Mei for DAQ & Online

  3. Online Calibration manage • To reduce calibration time for data reconstruction • New scripts allow T0gmake2 (f08, end of run) to submit two processes “calib_ene” and “calib_time” to a given machine now is f34. • Calibmon_db2 (f04) • TCL interface monitoring online calibration flags from DB2, started by RUNCTL W. Mei for DAQ & Online

  4. “ll” package (Load Leveler) that is running in all offline machines as well as fibm08 (“llq –H” to get all help). • llstatus report all offline machine status • llq report job status in current machine. • llqk is allqalias, which is using frequently, reports step-id, step-name, job status, queue date, class and host. W. Mei for DAQ & Online

  5. Insert of T3filter • In the last week of data taking the trigger system was changed • Cosmic veto: flags all cosmic events but does not throw them away. • Cosmic events are analyzed by a software component-t3filter included in the main data flow • The main data flow on farm is: W. Mei for DAQ & Online

  6. Receive --> builder (B_T2_1_1) --> T3filter (B_1_1) --> recorder (main recorder) • Most of the monitoring processes take data from the builder buffer which is now B_T2_1_1 • T3filter also collects 1/64 of random cosmic events for system studies W. Mei for DAQ & Online

  7. Many packages modified: • Farm package • Kid, for new buffer definition • Daqset, for creation new online process-t3filter • Runctrol and graphic interface (build events = ~3.6Khz before t3filter, total events = ~2.0Khz after t3filter on disk) • Monitor packages W. Mei for DAQ & Online

  8. DAQ real run with t3filter • Part history of runs on Dec. 7th. with T3filter • 0.3 – 2.8MB/s, chain (10MB — 13MB/s in total), • Use of the total CPU on a farm • Overview of the system within beam lost compare with normal status W. Mei for DAQ & Online

  9. W. Mei for DAQ & Online

  10. W. Mei for DAQ & Online

  11. Receiver buffer c10 c1 c2 c3 builder t3filter recorder W. Mei for DAQ & Online

  12. W. Mei for DAQ & Online

  13. W. Mei for DAQ & Online

  14. Conclusion • DAQ works well (10-13MB/s) 3.6Khz acquired, 2.0Khz written on disk • No limit from system resources • idle time 33%-55% depending on archiving status. Wait time is almost zero • Is able to extend to higher throughput without problem W. Mei for DAQ & Online

More Related