Container element for settings that control the execution of the participant. Provides the information needed to start the coupling participant.
Optional. If this element does not exist, System Coupling populates the ExecutionControl part of the data model with values based on the participant type.
Contains the following sub-elements:
<ExecutionControl> <InitialInput/> <Command/> </ExecutionControl>
Defines the name of the solver input file to be used for the initial run of the coupled analysis.
Required if the parent <ExecutionControl> element exists.
Acceptable <InitialInput> values vary according to coupling
participant:
For an AEDT participant, it must refer to a solver input file (.py), which in turn refers to an Ansys Electronics Desktop project file (.aedt).
For a CFX participant, it must refer to a CFX-Solver input (.def or .res) file.
For a Mechanical participant, it must refer to a Mechanical APDL solver input file (.dat).
For a Fluent participant, there are two options:
It can refer to a Fluent case file (.cas, .cas.gz, or .cas.h5), either with or without the extension. In this case, System Coupling generates its own Fluent journal script to read this case file.
It can refer to a custom Fluent journal file (.jou). The journal file must have a .jou extension.
Specifies the command that can be used to start the coupling participant automatically.
Optional. Note that this element is not included when a participant generates its System Coupling Participant (.scp) setup file because System Coupling can locate the participant's execution command based on other information from the file.
To obtain the command used to start a participant, run GetExecutionCommand() for the participant. For participant-specific details, see the participant's documentation on executing from the command line.