When restarting a coupled analysis in the System Coupling CLI, the steps vary according to whether the analysis is being restarted from final or an intermediate restart point. For more information, see:
To restart a coupled analysis from the final restart point in the System Coupling CLI, perform the following steps:
Run the Open() command without arguments.
Tip: If your Restart files are not saved to the default SyC directory, then use the optional FilePath argument to specify the directory.
By default, System Coupling finds the last coupling step or iteration completed in the previous run and loads all information (both for System Coupling and participants) required to restart from that step or iteration.
If the previous run completed, extend the analysis using the NumberOfSteps or EndTime setting (defined under SolutionControl).
If desired, make any necessary changes to analysis settings for System Coupling and/or participants.
Changes saved prior to the restart (either in System Coupling or in any participant except Mechanical) are written to the Settings file and included in the restarted run.
Start the solution using your preferred solve process (using either the Solve() command or interactive solve commands).
System Coupling automatically starts all participants from the last completed coupling step or iteration and continues the solution with the next step or iteration.
To restart a coupled analysis from an intermediate restart point in the System Coupling CLI:
Run the Open() command with the CouplingStep or CouplingIteration argument set to the number of the step or iteration from which you want to restart the analysis.
Tip:By default, the dialog opens to the SyC working directory. If your Restart files are not saved to the default SyC directory, then use the optional FilePath argument to specify the directory.
Restart files may have been generated for either coupling steps or coupling iterations, based on the type of the analysis and whether the participants involved support the creation of restart points per iteration. For more information, see Restart Files.
System Coupling automatically finds the specified coupling step or iteration and loads all information (both for itself and participants) required to restart from that step or iteration.
Note: If the files for subsequent restart points cannot be removed, then System Coupling generates an exception message instructing you to free up the files and reissue the Open() command with the CouplingStep or CouplingIteration argument.
If desired, make any necessary changes to analysis settings for System Coupling and/or participants.
Changes saved prior to the restart (either in System Coupling or in any participant except Mechanical) are written to the Settings file and included in the restarted run.
Start the solution using your preferred solve process (using either the Solve() command or interactive solve commands).
System Coupling automatically starts all participants from the specified coupling step or iteration and continues the solution with the next step or iteration.