search

cmsdaq / DAQExpert

New expert system processing data model produced by DAQAggregator
1 stars 2 forks source link

Special instructions: Pixel OOS #192

Closed gladky closed 6 years ago

gladky commented 6 years ago 
  * If PIXEL FED is OOS:
     * Try Pause and Resume.
     * If this doesn't solve the problem: stop the run, green recycle PIXEL and start new run (recovery button of L0A with tick on PIXEL green recycle).
     * If also this does not resolve the problem: stop the run, red recycle PIXEL and start new run (recovery button of L0A with tick on PIXEL red recycle).
gladky commented 6 years ago

Current default instructions coming from "Partition problem" (FlowchartCase3) for subsystem going OOS (includes Pixel)

  1. Issue a TTCHardReset
  2. 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)
  3. Problem fixed: Make an e-log entry
  4. Problem not fixed: Try to recover: Stop the run. Red & Green recycle the subsystem {{SUBSYSTEM}}. Start a new run. Try up to 2 times
  5. Problem still not fixed after recover: Call the DOC of {{SUBSYSTEM}} (for the partition in {{STATE}})
  6. Problem fixed after recover: Make an e-log entry. Call the DOC of {{SUBSYSTEM}} (for the partition in {{STATE}}) to inform

Condition to fire this:

gladky commented 6 years ago

Current default instructions coming from "Out of sequence data received" (includes Pixel)

  1. Try to recover (try up to 2 times)
  2. StopAndStartTheRun
  3. Problem not fixed: Call the DOC of {{PROBLEM-SUBSYSTEM}} (subsystem that caused the SyncLoss)
  4. Problem fixed: Make an e-log entry. Call the DOC {{PROBLEM-SUBSYSTEM}} (subsystem that caused the SyncLoss) to inform about the problem
gladky commented 6 years ago

We could introduce PIXEL specific instructions for this case:

  1. Try Pause and Resume.
  2. Problem not fixed: stop the run, green recycle PIXEL and start new run
  3. Problem still not fixed: stop the run, red recycle PIXEL and start new run
  4. Problem fixed: Make an e-log entry.

Note:

gladky commented 6 years ago

Please confirm that's up to date.

hsakulin commented 6 years ago

Proposed changes are fine according to Benedikt.

gladky commented 6 years ago

Introduced with 2.13.1, moved to section "covered by expert" in bulletin board