Skip to content

Conversation

@knopers8
Copy link
Collaborator

When ECS2DCS2ECS is used as the DCS server, one can specify expected reply to requests by adding "STATE_SEQUENCE" to request extra parameters with a key formatted as below:

MILLIS_DELAY:DETECTOR_STATE[,MILLIS_DELAY:DETECTOR_STATE]*

This commit exposes a possibility to set these sequences via configuration parameters. Essentially, this allows us to have some configurations on staging which use DCS with pre-defined state sequences.

When ECS2DCS2ECS is used as the DCS server, one can specify expected reply to requests by adding "STATE_SEQUENCE" to request extra parameters with a key formatted as below:
```
MILLIS_DELAY:DETECTOR_STATE[,MILLIS_DELAY:DETECTOR_STATE]*
```
This commit exposes a possibility to set these sequences via configuration parameters.
Essentially, this allows us to have some configurations on staging which use DCS with pre-defined state sequences.
@knopers8 knopers8 requested a review from justonedev1 as a code owner May 22, 2025 13:30
@knopers8 knopers8 changed the title [core] allow to specify a test state sequence upon DCS requests OCTRL-1026 [core] allow to specify a test state sequence upon DCS requests May 27, 2025
@knopers8 knopers8 merged commit 3de5be8 into AliceO2Group:master May 27, 2025
2 checks passed
@knopers8 knopers8 deleted the dcs-test-state-sequence branch May 27, 2025 06:53
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Development

Successfully merging this pull request may close these issues.

2 participants