Monitoring the TABs and GAB

updated: 23-Aug-05

Index

1. Monitoring in Run IIa
2. Monitoring & Testing in Run IIb
3. Monitoring & Testing Proposals

Monitoring in Run IIa

• See talks by Philippe Laurens and Bob Kehoe

Definition of Online Monitoring & Testing in Run IIb

Online Monitoring and Testing are defined as follows.

1. Monitoring:
   This class of information is collected from the TABs and GAB over VME when the Trigger Framework sends a CollectStatus request as part of the L1 Qualifiers sent with the SCL information for that L1 Accept. This happens approximately every 5 seconds.
2. Testing:
   These procedures are used to verify that the TABs and GAB are functioning properly: hardware is working, cabling is correct, algorithms produce expected output, etc.
3. TAB/GAB Status Registers:
   VME accessible registers containing status and error information at various points in the TABs and GAB.

Online Monitoring & Testing Proposals

1. 25-May-05: Some ideas for using the event memories as a basis for online monitoring and testing information.
   Note: this is only partially implemented in the current code.
2. 10-Mar-03: A proposal for online monitoring information from the TAB involving the calculation of means and RMS's for all TTs in the TAB firmware.
   Note: this is not implemented in the current code.