Process Synchronization and Analysis Evolution

The coupling service and participants advance synchronously through a coupled analysis. High-level synchronization is managed with the use of synchronization points, and low-level synchronization, between synchronization points, is managed using a token-based protocol.

The five primary synchronization points used to manage advancement through the coupled analysis are shown in Figure 6: Execution Sequence Diagram for the Coupling Service and Co-Simulation Participants. This figure also features notes regarding the processing that occurs between these points, as well as the coupling step and iteration loop structure. Each of these synchronization points, shown in dark gray, represents a gateway beyond which a given process may not advance until all other processes (or a subset thereof, as controlled by the coupling service) arrive. Note, as well, that while a process may serve data both between and at synchronization points, it may only request data between synchronization points.

Figure 6:  Execution Sequence Diagram for the Coupling Service and Co-Simulation Participants

Execution Sequence Diagram for the Coupling Service and Co-Simulation Participants

Details regarding processing between the Solution and Check Convergence synchronization points are shown in Figure 7: Processing Details for the Coupling Service and Co-Simulation Participants. During this stage of the analysis, the coupling service controls the advancement of co-simulation participants, or solvers, through two secondary synchronization points: Data Transfer and Solve, both shown in light gray. The sequencing of solvers is controlled by manipulating the relative order in which the solvers advance beyond these secondary synchronization points. For example, solvers with identical sequence indices all advance through the Data Transfer synchronization point together, and then do the same for the Solve synchronization point.

Figure 7:  Processing Details for the Coupling Service and Co-Simulation Participants

Processing Details for the Coupling Service and Co-Simulation Participants

These figures highlight that all participants traverse the duration of the entire coupling step during each coupling iteration. They have complete freedom, however, to traverse the coupling step duration in one or more ‘solver’ steps, each of which may include one or more solver iterations. If multiple ‘solver’ steps are used within one coupling step, then this is referred to as sub-stepping (or sub-cycling). Review the participant systems’ documentation to see if sub-stepping occurs and is supported with System Coupling.


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