pareto chart of locklosses by cause/tags, and downtime by lockloss cause
This is a request from Jeff Jones, with the goal of helping to decide where to spend time trying to address operational issues. Pareto_chart
The idea would be to categorize our locklosses, and graphically display which ones are most common. Niko and I talked about this. We would like to have each lockloss in only one category to avoid double counting, so for locklosses which fit into multiple categories we'd want to use a hierarchy of tags. So if the lockloss happens during maintenance, we categorize it as maintenance and ignore all other tags:
- maintenance
- ADS_excursions
- BOARD_SAT
- BRS_GLITCH
- seismic
- windy
- un-categorized
Combining this information with the time until we relock (until we get back to the state 600) would be a way to make a chart that accounts for our down time.