If a text file named scStop.stop is found in the coupling service’s run directory, then the service will shut down as soon as possible. The shutdown file should contain two (or more) lines as shown below:
0 The reason for terminating the analysis
The first line contains an integer flag that indicates whether or not the termination should be interpreted as an ‘interrupt’ or as a ‘stop’.
With an integer value of 0, the analysis will be interrupted; the coupling service will complete the current coupling step and signal the co-simulation participants that the execution has ended. This will cause the coupling service and participants to shutdown cleanly.
With an integer value of 1, the analysis will be stopped; the coupling service will signal the co-simulation participants to abort the run as quickly as possible. This will not produce a clean shutdown.
The second and subsequent lines in the file are reported in the coupling service’s log file when summarizing the reason for shutting down the coupled analysis.