Closed gladky closed 5 years ago
Currently if partition (including CSC's ones) goes to error state (or OOS) we will detect it with "Partition Problem" LM. It will suggest:
- Issue a TTCHardReset",
- If DAQ is still stuck after a few seconds, issue another TTCHardReset (HardReset includes a Resync, so it may be used for both OOS and ERROR)",
- Problem fixed: Make an e-log entry",
- Problem not fixed: Try to recover: Stop the run. Red & Green recycle the subsystem {{SUBSYSTEM}}. Start a new run. Try up to 2 times",
- Problem still not fixed after recover: Call the DOC of {{SUBSYSTEM}} (for the partition in {{STATE}})",
- Problem fixed after recover: Make an e-log entry. Call the DOC of {{SUBSYSTEM}} (for the partition in {{STATE}}) to inform"
The problem description would be:
Partition {{TTCP}} in {{SUBSYSTEM}} subsystem is in {{STATE}} TTS state. It's blocking triggers."
That complies with special instructions with CSC so I would propose to move it to section "Covered by expert"
Moved to "Covered by expert" section