Co-Simulation Participants Sequencing

In general, the driver of the physical problem should be processed first (that is, given a lower sequence index). If, in a fluid-structure interaction (FSI) simulation, the fluid flow (such as air flow around a wing) causes the structure (that is, the wing) to deform, then the fluid analysis should be first in the processing sequence.

The System Coupling infrastructure allows the co-simulation of multiple coupling participants. In many cases, the execution (for example, solve) sequence of the co-simulation participants is inconsequential. In some cases, however, the sequence may affect solution stability and/or the time required to execute the complete coupled analysis.


Note:  To improve solution stability, sequential solutions are used by default. To facilitate synchronization of interface geometry, participants that consume geometrical or mesh deformations (e.g., the Fluids solver in a Fluid Structure Interaction analysis) are executed last.


Controlling Participant Sequencing

Participant sequencing controls the order in which co-simulation participants collect data (as prescribed by defined data transfers) and execute their part of the coupled analysis. Ordering is specifically controlled by assigning a sequence index to each of the co-simulation participants. Participants with the smallest sequence index are processed first. If two (or more) participants are assigned the same sequence index, they are processed simultaneously (that is, required data is first collected from other participants, and then the participants all execute (for example, solve) simultaneously.

Care is taken to ensure that the geometry and mesh are properly synchronized at the end of each coupling step for all co-simulation participants. This is required to ensure consistency during post-processing and during restarts. An extra ‘partial’ coupling iteration reprocesses all participants that are targets of deformation or motion-related data transfers. An extra partial iteration is executed once after all convergence targets are met or the maximum number of coupling iterations for the step is realized. A warning that extra partial iterations will be performed is provided in the validation output that follows the setup summary in the System Coupling Service Log File (scLog.scl_, scLog_##.scl).

When an extra 'partial' coupling iteration is used to properly synchronize the interface geometry and mesh, there will be no noticeable change in the geometry and mesh during the first coupling iteration of the subsequent step. In this case, the system coupling chart output will have near-zero values for the change in motion for the related data transfer values.

Using Sequencing to Reduce Coupled Solution Execution Time

As noted above, all co-simulation participants that share the same sequence index will collect data and execute their respective parts of the coupled analysis at the same time. This is a way of parallelizing the coupled solution process and potentially reducing the overall execution time of the coupled analysis. However, convergence difficulties (for example, more coupling iterations per step) and possible divergence may occur when multiple participants run simultaneously. This is because each participant in the group that is solved simultaneously collects and uses less up-to-date information from other participants. The stronger the physical coupling between each participant is, the more likely convergence difficulties will be encountered if the participants are processed simultaneously.


Release 18.2 - © ANSYS, Inc. All rights reserved.