Aborting an Analysis
To end the solution process before it is complete:
- Right-click In the Progress window and click Abort or click on drop-down button next to progress bar(s).
The solver ends the analysis immediately.
The solver ends the analysis immediately. The data for the currently running adaptive pass, frequency point, time step, or variation is lost. Previously completed solutions may or may not be retained (depending on what process was interrupted by the Abort command). If you want to ensure that the results of all completed solutions are saved, use Clean Stop instead of Abort.
To abort the solution process after the current
- Right-click the Progress window, or click on drop-down button next to progress bar(s) and click Clean Stop on the shortcut menu.
The analysis ends after the currently running adaptive pass, frequency point, time step, or variation has been solved. Solutions completed before the stop request are retained.
If you request a clean stop during the third adaptive pass, the solution for the third pass will be available once the third pass has finished solving, but the fourth pass will not run.
Ansys EM Application as an LSF Job
If you have an Ansys EM application running as an LSF job, you can use the command "bkill -s SIGTERM jobid" to terminate that application. Here jobid is the LSF job id. The response will be "Job <jobid> is being signaled". The response is the same whether the job is actually being signaled or not.
In cases where the SIGTERM parameter is ignored, the command kills the LSF job, but does not clean the lock files, and other files may not be in a consistent state.
Linux
For Linux, you can use TERM commands. Sigterm handling
is done in the Desktop library. You can abort a running batchsolve
by sending a TERM signal to