Skip to content

Update operation_order.md with trg.RunStop change #646

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
teo merged 1 commit into from
Jan 9, 2025
Merged

Update operation_order.md with trg.RunStop change #646

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
5 changes: 3 additions & 2 deletions docs/handbook/operation_order.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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

Expand Down Expand Up @@ -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`.
will move to `ERROR`.