Closed gladky closed 6 years ago
contacted Jose Ruiz
For reference:
The instruction is from one year ago, so I am not aware if the instruction is up-to-date but I don't think so:
- Is this up to date?
I would check with the expert for FED 1404 subsystem, that I don't remember right now to whom it belongs, but I would guess L1 DOC....
- Is "fed stop sending data" equivalent to FED being in warning/busy state and having 0 backpressure? Or should I understand it differently?
if I remember correctly it means if the shifter sees 0 triggers coming out from FED 1404, independently of the state of the FED.
FED 1404 is uGT (micro Global Trigger) according to #182
Hi, I don't think uGT needs to be treated specially anymore. I remember the DAQ expert already has instructions for such a situation (i.e. FED xyz stops sending data, after a while DAQ exerts backpressure on some other FED), can you remind me what this was?
Cheers, Dinyar
Do you mean this:
RU {{AFFECTED-RU}} is stuck waiting for FED {{PROBLEM-FED}}. Problem FED(s) belong(s) to partition {{PROBLEM-TTCP}} in {{PROBLEM-SUBSYSTEM}} subsystem. This causes backpressure at FED {{AFFECTED-FED}} in other FED-builder {{AFFECTED-FED-BUILDER}} of subsystem {{AFFECTED-SUBSYSTEM}}. Note that there is nothing wrong with backpressured FED {{AFFECTED-FED}}
with a recovery action:
- Try to recover: Stop the run
- Red & green recycle the subsystem {{PROBLEM-SUBSYSTEM}} (whose FED stopped sending data)
- Start new Run (Try 1 time)
- Problem fixed: Make an e-log entry. Call the DOC of the subsystem {{PROBLEM-SUBSYSTEM}} (whose FED stopped sending data) to inform
- Problem not fixed: Call the DOC for the subsystem {{PROBLEM-SUBSYSTEM}} (whose FED stopped sending data)
from RUStuckWaitingOther LM
Yes, that's it. This can be used also for uGT (1404), I don't remember exactly what triggered that entry in the shifter instructions, but we haven't had any readout problems with the uGT in the past few months that would warrant special instructions.
In this case this will be deleted from shifter bulletin board. I guess there is no need to keep it in section "deprecated" or "outdated", right @hsakulin ?
removed.