SLAC PEP-II
BABAR
SLAC<->RAL
Babar logo
HEPIC E,S & H Databases PDG HEP preprints
Organization Detector Computing Physics Documentation
Personnel Glossary Sitemap Search Hypernews
Unwrap page!
Det. Search
Who's who?
Meetings
FAQ
Images
Archive
Systems
Performance
Intern. region
Vertex Tracker
Drift chamber
DIRC
Calorimeter
IFR
LST
Magnet
Electronics
Trigger
Operations
Run Coordination
Contact Experts
Shift Takers Info
Operations Manual
Electronic Logbook
Ops Hypernews
Shift Signup
Check this page for HTML 4.01 Transitional compliance with the
W3C Validator
(More checks...)
DIRC FAST MONITORING

The Fast Monitoring is an important component of the DIRC monitoring. Parallel to the data taking in IR2, the status of the different components of BaBar (subdetectors, L1 and L3 triggers, dataflow, Trickle Injection system) are monitored through the Fast Monitoring system which has two main components.

  • The real-time monitoring which is the responsability of the DQM who is looking at a set of component-dependent histograms through a JAS interface. The histograms (for the DIRC, various occupancy and timing plots plus a summary of the online errors) are accumulating data over the current run and cleared at the startup of a new run.
    The corresponding DIRC packages are DrcOfm and DrcMonTools.
  • In addition to the histograms displayed on the DQM JAS pages, several other histograms are filled during the run and then written in an hbook file located in a directory whose generic name is
    /nfs/bbr-srv02/u4/Monitoring/OutputArchive/YYYY/MM/LiveFastMon.
    The hbook names are generated using the following convention:
    LiveFastMon-00<run number>-YYYYMMDD-<time>.hbook where <time> is the time at which the fast monitoring starts to accumulate data (usually at most 1-2 minutes after the beginning of the run).
    Once the LiveFastMon stream has been created, an automatic post-processing starts and analyzes in particular the DIRC histograms (through the package DrcOfmPostProcess). The output of this job is a postscript file which must be checked offline by the DIRC oncall-expert to make sure that nothing has been missed by the shifters.
    Checking all such files is a mandatory task of the DIRC oncall expert.

The table below provides the main links related to the DIRC Fast Monitoring.

Last 200 runs processed by the Fast Monitoring List of all runs processed in 2005
(since the new framework is operational)
Fast Monitoring documentation List of all runs processed in 2006


This page is maintained by Nicolas Arnaud
Last significant update: October 06 2005