From 8753d50761a91254fe4efa4f3075bfb6f62d39af Mon Sep 17 00:00:00 2001 From: Piotr Konopka Date: Mon, 24 Mar 2025 12:20:00 +0100 Subject: [PATCH] [doc] Update DCS PFR documentation As done in https://github.com/AliceO2Group/Control/commit/56e07f5ff8db060cfe7c6b499f5eec02d27f6732 , PFR continues for PFR-compatible detectors, even if some are incompatible. --- docs/handbook/operation_order.md | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/docs/handbook/operation_order.md b/docs/handbook/operation_order.md index 4a861897..fdf05fa7 100644 --- a/docs/handbook/operation_order.md +++ b/docs/handbook/operation_order.md @@ -126,9 +126,9 @@ to the DCS service. If the grace period ends and at least one detector included in the environment is still incompatible with PFR, the PFR -operation **will not run for any detector**. +operation will be performed for the PFR-compatible detectors. -However, the environment +Despite some detectors not having performed PFR, the environment can still transition forward towards the `RUNNING` state, and any DCS activities that would have taken place in PFR will instead happen during SOR. Only at that point, if at least one detector is not @@ -142,8 +142,8 @@ with PFR as reported by the DCS service (or become compatible during the grace period), the PFR operation is immediately requested to the DCS service. -If this operation fails for one or more detectors, the -`dcs.PrepareForRun` call as a whole is considered to have failed, +`dcs.PrepareForRun` call fails if no detectors are PFR-compatible +or PFR fails for all those which were PFR-compatible, but since it is non-critical the environment may still reach the `CONFIGURED` state and transition forward towards `RUNNING`.