Skip to content

Fix link in operation_order.md #727

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
knopers8 merged 1 commit into from
Jul 1, 2025
Merged

Fix link in operation_order.md #727

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
4 changes: 2 additions & 2 deletions docs/handbook/operation_order.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,7 +1,7 @@
# Environment operation order

This chapter attempts to document the order of important operations done during environment transitions.
Since AliECS is an evolving system, the information presented here might be out-of-date, thus please refer to event handling in [environment.go][https://github.com/AliceO2Group/Control/blob/master/core/environment/environment.go) and plugin calls in [ControlWorkflows/workflows/readout-dataflow.yaml](https://github.com/AliceO2Group/ControlWorkflows/blob/master/workflows/readout-dataflow.yaml) for the ultimate source of truth.
Since AliECS is an evolving system, the information presented here might be out-of-date, thus please refer to event handling in [environment.go](https://github.com/AliceO2Group/Control/blob/master/core/environment/environment.go) and plugin calls in [ControlWorkflows/workflows/readout-dataflow.yaml](https://github.com/AliceO2Group/ControlWorkflows/blob/master/workflows/readout-dataflow.yaml) for the ultimate source of truth.
Also, please report to the ECS developers any inaccuracies.

## State machine triggers
Expand Down Expand Up @@ -99,4 +99,4 @@ This is the order of actions happening at a healthy end of run.
- `"run_end_completion_time_ms"` is set using current time. It is considered as the EOEOR timestamp.
- `after_STOP_ACTIVITY` hooks with positive weights (incl. 0) are executed:
- `ccdb.RunStop()` at `0`
- `bookkeeping.UpdateRunStop()`, `bookkeeping.UpdateEnv()` at `+100`
- `bookkeeping.UpdateRunStop()`, `bookkeeping.UpdateEnv()` at `+100`
Loading