Monitoring and Alarms

• TCC is a Server of Raw Monitoring Information

Client Monitoring Application will interpret and display data

• Provide view of current operation of the system

 
• Show what and how well the system is doing
• whole event available (rebuilt)
• additional diagnostics scalers
• additional status information
• e.g.  Run I L1CT Trigmon Doc: www.pa.msu.edu/hep/d0/ftp/run1/monitoring/trgmon.txt

 

 

• Show enough information to diagnose problems

when the system is not working properly
 
• Maybe also include current resource programming
• debugging, diagnostics and commissioning tool
• close the loop and allow user to verify chain of command

 
• Take Snapshot contemporary accross whole L1CT

  (and accross other systems, e.g. L1 FW)
• Listen to SCL and be ready to capture Triggered Crossing
• Distributed throughout whole system, Centrally controlled
• Zero effect on data taking
• Read snapshot at slow TCC IO speed
• Fallback ability to force immediate monitoring data capture

 
• TCC arranges to capture new snapshot every ~5 sec

 

Alarms

• TCC also a Relay for hardware Alarms
• Show detail of problems that may be detected by hardware

(or software)
• anything detected in hardware (e.g. cable fell off, drift, etc)

can be reported to D0 centralized Significant Event System
and presented to experts