Execution Control has the following capabilities:
The System Coupling system offers comprehensive control over the sequencing of co-simulation participants, and specifically over the data transfers that are required to obtain a solution. This is controlled through the settings in the Co-Sim Sequence. The participants are sequenced by assigning a sequence value, which is an integer value between 1 and the number of participants in the analysis, to each participant. Each participant executes its solutions (that is, all required data transfers, followed by obtaining the equation solution) in the order of its sequence value, where the participants with the lower sequence values execute first. The coupled analysis will use sequential solutions or simultaneous solutions, depending on the assigned sequence values. This is described in more detail below.
Note: To improve solution stability, sequential solutions are used by default. Note as well that, to facilitate synchronization of interface geometry, participants that consume geometrical or mesh deformations (for example, the Fluids solver in a Fluid Structure Interaction analysis) are automatically assigned larger sequence values by default.
Additional information can also be found in Best Practice Guidelines for Using System Coupling.
A sequential solution is done when all co-simulation participants are assigned different solution sequence values. In particular, participants perform their solutions (that is, all required data transfers, followed by obtaining the equation solution) in the order of the sequence values specified in the user interface. Sequential solutions are optimal for analyses that involve strong physical couplings, because the most recent information from one participant is always used by subsequent participants. This typically translates into requiring the fewest coupling iteration per coupling step to reach a converged solution. However, it may not yield the shortest (wall-clock) solution time if the participants are run on different CPUs.
A simultaneous solution is done when one or more co-simulation participants are assigned identical solution sequence values. In particular, when the same sequence value is applied to multiple participants, then all those participants perform their respective data transfers, after which those same participants perform their equation solutions simultaneously.
Simultaneous solutions are optimal for analyses that involve weak physical couplings because the most recent information from one co-simulation participant is not required by other simultaneously executed participants in order to reach a converged solution. Additionally, the overall (wall-clock) solution time may be reduced if the simultaneously executed participants are run on different CPUs. However, if used with co-simulation participants that exhibit strong physical couplings, simultaneous solutions may adversely affect the rate of convergence, and possibly lead to divergence.
The Debug Output entity under Execution Control in the outline model controls the level of debug information written in the System Coupling Log (*.scl) file during the execution of the solution. The basic level of detail included is controlled using one of the following levels:
None
Level 1
Level 2
Level 3
Level 4
All Levels
By default, the value set for the Global Level is applied to all stages of solution execution listed below. To use a different value for one or more of the specific stages of solution execution, change the value from Use Global Level to the desired output level.
Note that stages of solution execution that are associated with Data Transfers are grouped together, and have their own default Data Transfers Level value. To use a different value for one or more of these stages of solution execution, change the value from Use Data Transfers Level to the desired output level.
The following properties control the debug level for different sections of the log:
Controls the level of output from the start of the coupling service until creation of the "Summary of SC Setup" banner in the SCL file.
Controls the level of output from the end of the setup validation until the Initial Synchronization synchronization point (that is, between the Setup Validation and System Coupling Summary banners).
Controls the level of output from the end of the setup validation until the Analysis Initialization synchronization point (that is, between the System Coupling Summary and Solution banners).
Controls the level of output during the setup of coupling steps and coupling iterations. This output does not include information related to the data transfers.
Specifies the debug output generated for data transfers. Note that header information for mapping is generated whenever the mesh coordinate or mesh topology output is requested. Similarly, header information for the data transfers is generated whenever the transfer data output is requested.
Provides the default level for the different debug output controls in the Data Transfers group. If the debug level of any property in the Data Transfers group is set to Default, then the debug level of that entry is governed by the level set here. If the Data Transfers Level itself is set to Use Global Level, then it derives its value from the default level defined for all debug output controls.
Controls the level of output for mesh coordinates of the source region in all data transfers.
Controls the level of output for mesh topology (elements and nodes) of the source region in all data transfers.
Controls the level of output for the source data in all data transfers.
Controls the level of output for mesh coordinates of the source region in all data transfers.
Controls the level of output for mesh topology (elements and nodes) of the source region in all data transfers.
Controls the level of output for the target data in all data transfers.
Controls the level of output from the Check Convergence synchronization point until the next synchronization point, which may be either Shutdown or Solution.
Controls the level of output after the Shutdown synchronization point.
For information about synchronization points, see Process Synchronization and Analysis Evolution.
Note: The debug level for all the properties, except Default, can be set at any level. For the Default property, the available levels are from None to All Levels. Increasing levels always generate more detailed output. Note, as well, that the output level settings for each of the mesh coordinates, topology, and transfer data, control the number of lines of output generated. Specifically, 10 L lines of data will be written for an output level setting of L (for example, 100 lines will be written for an output level of 2, or Level 2).
The Intermediate Restart Data Output entity under Execution Control in the outline model allows the selection of time points at which restart data should be generated during the execution of the solution. Depending on the participant, the restart data may or may not be the same as the results data. Writing of results data for post-processing should be set from within the participant setup cell.
Important: During execution of the coupled analysis, co-simulation participants will automatically be requested to generate intermediate restart data at the same frequency as the System Coupling service. Note that this feature only affects the frequency at which data is generated; the content of data is determined by the participant. To see if this feature is supported, see Supported System Coupling Participants.
Choose one of the following options to control when restart data is produced.
No intermediate restart output files are generated using this option. This option is enabled by default.
Restart output files are generated at the end of each coupling step.
Restart output files are generated at the end of the coupling steps corresponding to the interval specified in the Step Interval box below.
Note: If you specify a Step Interval that is above or below the allowed limit, an error is displayed; change the Step Interval as required.