search

cmsdaq / DAQExpert

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

Special instructions: HF and PIXEL in running degraded #189

Open gladky opened 6 years ago

gladky commented 6 years ago

1

  • if HF goes into in running degraded for more than two minutes and the jet trigger input rate is higher than normal (check with trigger shifter), call the HCAL DOC (A.Perieanu, 2017-06-17). After the trigger rate is back to normal the HF could stay for 8-9 minutes in Running degraded state, beyond that the HCAL doc should be called (updated by Jose Ruiz 26-06-2017). There is a script trying to resolve the issue automatically, so only call the HCAL DOC if the trigger rate is still high after two minutes (see http://cmsonline.cern.ch/cms-elog/991664 ).

2 (already covered by expert)

If PIXEL goes into Running Degraded call PIXEL DOC. At nighttime, wait 12 minutes, to see if it recovers itself. (Alessandro Di Mattia 04-10-2017)

gladky commented 6 years ago

Currently we do not provide any instructions in case subsystem goes to running degraded state.

  1. Is is still up to date?
  2. Shall we include this in expert instructions?
  3. If so: where do we take jet trigger input rate from and what's "higher than normal"?
hsakulin commented 6 years ago

Please contact HCAL about the first part. For the second part, the feedback is in #195.

gladky commented 6 years ago

We are now (from 2.13.1 onwards) providing following default instructions for running degraded:

{{PROBLEM-SUBSYSTEM}} subsystem is in running degraded

  1. Please check the message in the subsystem information section in the Level-0 FM for subsystem {{PROBLEM-SUBSYSTEM}}. It should contain a description of the problem.
  2. Use your common sense to decide whether a human expert needs to look at the problem or whether CMS can continue taking data despite the problem.
  3. If there is no problem description or if the description is unclear, call the DOC of subsystem {{PROBLEM-SUBSYSTEM}}.
gladky commented 6 years ago

@jkunkle could you please comment on the first part?