From 7179244e1913e88c235302163e36e0a8f41fd2e0 Mon Sep 17 00:00:00 2001 From: Piotr Konopka Date: Thu, 9 Jan 2025 11:06:03 +0100 Subject: [PATCH] Update operation_order.md with trg.RunStop change According to the change in https://github.com/AliceO2Group/ControlWorkflows/pull/670 --- docs/handbook/operation_order.md | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/docs/handbook/operation_order.md b/docs/handbook/operation_order.md index b4fe3f56..4a861897 100644 --- a/docs/handbook/operation_order.md +++ b/docs/handbook/operation_order.md @@ -54,9 +54,10 @@ This is the order of actions happening at a healthy end of run. ### before_STOP_ACTIVITY - `before_STOP_ACTIVITY` hooks with negative weights are executed + - `trg.RunStop()` at `-10` - `"run_end_time_ms"` is set using the current time. It is considered as the EOR and SOEOR timestamps. - `before_STOP_ACTIVITY` hooks with positive weights (incl. 0) are executed: - - `trg.RunStop()`, `odc.Stop()` (does not need to return now) at `0` + - `odc.Stop()` (does not need to return now) at `0` ### leave_RUNNING @@ -194,4 +195,4 @@ If this operation fails for one or more detectors, the The environment will then declare a **failure**, the `STOP_ACTIVITY` transition will be blocked and the environment -will move to `ERROR`. \ No newline at end of file +will move to `ERROR`.