Thursday, June 05, 1997 Block of data serviced by TCC for the L2 Global ----------------------------------------------- We are thinking here about all types and classes of information. This is in no way a complete list. Just a first shot. 1. Monitoring data (some fixed format block read out every 5 sec) scalers sptrg scalers L2 input count (possibly rely solely on L1FW) L2 Pass count (possibly rely on L2 FW) MFP count (possibly done in L1FW) tool scalers try pass fail processing time overall performance scalers number of cycles number of skip number of pass, fail number of input format errors number of process error number of MFP input fifo empty at end of event input fifo full, delay transfer of next event output fifo empty event processing time (last event, average, min/max...?) time wait between events Magic Bus busy ratio processing duty ratio VBD readout duty ratio programming which sptrg has filters attached how many tools for each sptrg states running/waiting or monit data fresh/stale number of events in input fifo number of events in output fifo VBD state and status 2. Run Log information (stuff you want to end up in a file on TCC) Programming feedback (with time stamps) start /stop run (if known) Tool Initialization OK or problems Heartbeat time stamp 3. Operation Error/Warning/Information messages (variable, asynchronous messages serviced every 5 sec) Global No Sptrg need processing = Skip Notice long time since last event No input buffer slot available, delay event read No output buffer slot availble, delay event processing Input event pieces don't match (error goes to SCL, but report anyway) data format, checksum communication problem with Worker Sptrg Pass Rate too high Pass Rate too low Tool Pass Rate too low/high Expected input not found (e.g no candidates) Too many candidates, overflow Output communication problem with Worker formatting VBD problem 4. Immediate Attention from TCC (something that can't wait 5 second AND that TCC can do something about) (if only the DAQEXP can help, maybe no need to interrupt TCC) L2 FW decision doesn't match the pass/fail L2 Answer Panic, L2 system hosed, no more 5s information or automatic recovery