Context
The cosmics run with the barrel at SR1 has taught us more about the sorts of information we require from the online monitoring process during physics running.The purpose of the online monitoring is to provide feedback to the online operators, and to a monitoring shift crew about the conditions of the detector.
Required features
The monitoring framework should:- provide an idl interface which describes the funtionality it provides to other processes.
- respond to IPC requests from the SCT GUI to display on the main SCT display occupancy plots, hitmaps, efficiencies etc.
- histogram error rates
- BD - be able to make "summed" histograms, if not by default, then upon request. ie. ROD/Barrel occupancy/error rates.
- AJB - suggestion for implimentation of above. Process keeps map<strip_offlineid,nhits> for each lumi block. This is possible in memory: ~32bits*6M strip*2 ~ 50 Mbytes of memory required.
- respond to IPC request asking to place summary information (such as average occupancies or error rates per module or per chip) into the online information service.
- provide time-line information about variations in occupancy within a run and between runs.
- provide list of the 'n' most noisy channels, and their noise
- be able to provide occupancy/error rate/efficiency histograms for some short time period in the past (e.g. the last 10 seconds or the last n events).
- PWP - during final operation, should this be tied to the luminosity block?
- be able to provide comparison/reference distributions on IPC request
- provide data displayers which are compatible with the SCT web display.
When the CORAL/COOL implimentation of the configuration service is available, the monitoring should use this as its source of configuration information.
-- AlanBarr