Skip to content

Commit 8753d50

Browse files
authored
[doc] Update DCS PFR documentation
As done in 56e07f5 , PFR continues for PFR-compatible detectors, even if some are incompatible.
1 parent a192490 commit 8753d50

File tree

1 file changed

+4
-4
lines changed

1 file changed

+4
-4
lines changed

docs/handbook/operation_order.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -126,9 +126,9 @@ to the DCS service.
126126

127127
If the grace period ends and at least one detector
128128
included in the environment is still incompatible with PFR, the PFR
129-
operation **will not run for any detector**.
129+
operation will be performed for the PFR-compatible detectors.
130130

131-
However, the environment
131+
Despite some detectors not having performed PFR, the environment
132132
can still transition forward towards the `RUNNING` state, and any DCS
133133
activities that would have taken place in PFR will instead happen
134134
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
142142
the grace period), the PFR operation is immediately requested to the
143143
DCS service.
144144

145-
If this operation fails for one or more detectors, the
146-
`dcs.PrepareForRun` call as a whole is considered to have failed,
145+
`dcs.PrepareForRun` call fails if no detectors are PFR-compatible
146+
or PFR fails for all those which were PFR-compatible,
147147
but since it is non-critical the environment may still reach the
148148
`CONFIGURED` state and transition forward towards `RUNNING`.
149149

0 commit comments

Comments
 (0)