search

cmsdaq / DAQExpert

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

Special instructions: Pixel FED stuck #193

Open gladky opened 6 years ago

gladky commented 6 years ago
  • If the pixels are stucking the run due to a particular FED, and if we are not in stable beam, let the run ongoing and call the pixel experts, they would like to see what is going on and they cannot do it if the run is stopped and the pixels recycled (Matthieu Marionneau 14-07-2017)
hsakulin commented 6 years ago

this seems obsolete - but please check with benedikt vormwald (pixels), also for other pixel questions.

hsakulin commented 6 years ago

According to Benedikt this should be kept. Should the pixel DOC be called at any time of the day? I would propose that we should call the DOC for investigation only if we are before RAMP (i.ie. not in RAMP, FLAT TOP, SQUEEZE, ADJUST, STABLE BEAMS).

gladky commented 6 years ago

@bvormwald please confirm the following instructions. I also attach few examples when this would trigger from the past.

Instructions

In both cases we will show description of the problem: Partition {{PROBLEM-PARTITION}} of {{PROBLEM-SUBSYSTEM}} subsystem is blocking triggers, it's in {{TTCPSTATE}} TTS state. The problem is caused by FED {{PROBLEM-FED}} in {{FEDSTATE}}

Pixel specific instructions:

  1. Let the run ongoing and call the pixel experts, they would like to see what is going on and they cannot do it if the run is stopped and the pixels recycled
  2. Make an e-log entry

Default instructions:

  1. \<\<StopAndStartTheRun>> with <<RedAndGreenRecycle::{{PROBLEM-SUBSYSTEM}}>> (try up to 2 times)
  2. Problem fixed: Make an e-log entry. Call the DOC of the subsystem {{PROBLEM-SUBSYSTEM}} to inform
  3. Problem not fixed: Call the DOC for the subsystem {{PROBLEM-SUBSYSTEM}}

Note that \<\<ACTION>> indicates the auto-recovery actions that can be issued by DAQExpert automatically.

Examples from the past

In this cases we will now show the pixel specific instructions:

In this cases we will now show the default instructions: