Mystery MINOS DAQ outage of March 2014
MINOS DAQ suffered timing problems at both detectors, starting Sunday, March 9. The problem went away after the Near Detector was temporarily removed from the network.
It's still a mystery, and where wondering when it might come back...
Before we add much more to this Issue: does it inappropriately duplicate functionality that exists elsewhere? I'll give my own answers, but feel free to counter them:
1) It does not duplicate any experiment's ECL, since that is a time-based collection of information. It's a bit like standing on a bridge over a river watching things float by. Of course, search functions make that somewhat better, but it's never possible to get a complete overview of the history of an issue that took place over more than a shift, once a week or two have passed, from ECL. But one certainly can add links to specific ECL entries where appropriate.
2) It does not duplicate Service Now, since that is more service-oriented ("here's a problem, please fix it"). The purpose of this issue in redmine is to keep people actively working on the problem, and line management, informed, and aggregate information in a central place. And I believe redmine allows more flexibility in the kind of information that can be added, such as files, etc.