Difference between revisions of "Monitoring: Outline of Tasks and Issues"
From GlueXWiki
m |
(change to sections) |
||
| Line 1: | Line 1: | ||
| − | + | =Scope: what to monitor and why= | |
| − | + | # Online and near-online | |
| − | + | # Provide feedback to insure data quantity and quality | |
| − | + | # All relevant areas: | |
| − | + | ## GlueX Detector | |
| − | + | ## Detector electronics | |
| − | + | ## Hall D systems | |
| − | + | ## relevant Accelerator systems | |
| − | + | ## relevant IT systems | |
| − | + | ## relevant Facilities Management systems | |
| − | + | =Beyond scope: what should be done by other means= | |
| − | + | # Safety | |
| − | + | ## Personnel | |
| − | + | ## Equipment | |
| − | + | # Beam time accounting | |
| − | + | # Personnel training/certification/qualification | |
| − | + | # Shift-taking accounting | |
| − | + | # Shift-takers' refreshment supply | |
| − | + | =Types of data: how data is produced= | |
| − | + | # Event based: in the data stream | |
| − | + | ## Triggered detector events | |
| − | + | ## Special events | |
| − | + | # Slow controls: on-demand (usually), small data volume | |
| − | + | ## EPICS or EPICS-like devices | |
| − | + | ## stand-alone systems | |
| − | + | # Video | |
| − | + | # Web-based variables | |
| − | + | # Monitoring applications | |
| − | + | =Audience: who wants to know= | |
| − | + | # Counting room personnel | |
| − | + | # Accelerator personnel | |
| − | + | # Detector and systems experts | |
| − | + | # Collaborators | |
| − | + | ## On-site | |
| − | + | ## Off-site | |
| − | + | =Presentation: how to access the data= | |
| − | + | # Histograms | |
| − | + | # Strip charts | |
| − | + | # Web pages | |
| − | + | # Desktop applications | |
| − | + | # Audible alarms | |
| − | + | =Monitoring data collection programs: automated data consumers= | |
| − | + | # Alarm handlers | |
| − | + | # Archiver (database fillers) | |
| − | + | # Logbook | |
| − | + | =Time-scales= | |
| − | + | # Real time | |
| − | + | # Minute-by-minute | |
| − | + | # Hourly | |
| − | + | # Every shift | |
| − | + | # Every day | |
| − | + | # Weekly | |
| − | + | # Monthly | |
| − | + | # Run period | |
| − | + | # Annually | |
| − | + | ||
Revision as of 16:31, 3 April 2008
Contents
Scope: what to monitor and why
- Online and near-online
- Provide feedback to insure data quantity and quality
- All relevant areas:
- GlueX Detector
- Detector electronics
- Hall D systems
- relevant Accelerator systems
- relevant IT systems
- relevant Facilities Management systems
Beyond scope: what should be done by other means
- Safety
- Personnel
- Equipment
- Beam time accounting
- Personnel training/certification/qualification
- Shift-taking accounting
- Shift-takers' refreshment supply
Types of data: how data is produced
- Event based: in the data stream
- Triggered detector events
- Special events
- Slow controls: on-demand (usually), small data volume
- EPICS or EPICS-like devices
- stand-alone systems
- Video
- Web-based variables
- Monitoring applications
Audience: who wants to know
- Counting room personnel
- Accelerator personnel
- Detector and systems experts
- Collaborators
- On-site
- Off-site
Presentation: how to access the data
- Histograms
- Strip charts
- Web pages
- Desktop applications
- Audible alarms
Monitoring data collection programs: automated data consumers
- Alarm handlers
- Archiver (database fillers)
- Logbook
Time-scales
- Real time
- Minute-by-minute
- Hourly
- Every shift
- Every day
- Weekly
- Monthly
- Run period
- Annually
