Page Content

Description

The wait-to-go is a feature that allows to hold back the execution of the Orchestra system until some conditions are met, only before the first execution step of the clients models. Since it needs a few configurations, we will dedicate this document section to it.

The wait-to-go is driven by the framework. It is modelled as an output signal within the framework model, which can receive 2 values:

• 1 to activate the wait-to-go (blocking the execution of the clients connected to this framework)

• 0 to deactivate the wait-to-go (releasing the execution of the clients connected to this framework, allowing them to start working).

Activation and Use

In order to activate the wait-to-go feature in the OrchestraFramework I/O interface, the option 'Sync client at first step' needs to be unchecked:

Open

FIG 1: OrchestraFramework’s configuration to activate the wait-to-go feature

After saving the interface, the ‘WaitToGo’ signal should appear in the list of items available in the interface.

Open

FIG 2: Signals view with wait-to-go feature activated

This signal may be used as any other signal within the model. It can be manually modified or conditionally activated through some specific logic.

OrchestraClient Configuration

On the client side, there are no modifications to do inside the models. However, it is very important to check the option “Client performs wait to go during start()” in the configuration of the corresponding OrchestraClient I/O interface, as described in the document https://opal-rt.atlassian.net/wiki/spaces/PRD/pages/505446498.