The sections below walk you through the steps needed to restart a coupled analysis using System Coupling, but you will also need restart information specific to the participants connected to your System Coupling system. See Supported System Coupling Participants for a list of supported systems and references to their corresponding documentation regarding restarts.
Restarting a coupled analysis is further described in the following sections:
The System Coupling Results file generated by the coupling service contains all the information and data that are required to restart the coupling service only. Information and data that are required to restart the coupling participants, as well as the act of restarting those participants, are managed by the participants themselves.
The convergence history for a restarted run is generally not identical to that observed in a continuous run. There are two factors contributing to changes in convergence: interfaces are re-mapped upon restart, thereby changing the interpolation weights; and restart- and continuous-run convergence histories are not always identical (for example, the HHT transient discretization used by ANSYS Mechanical will not yield identical convergence histories while the Newmark discretization will).
Changes in convergence history across restarts will yield changes in solution values if solutions are not fully converged within coupling steps.