Reaction Time to Cancel Job

[sgold]

I started a job the other day, and realized after a short while that I missed an optimization step that would reduce my mesh, so I decided to cancel it.  It took some 20-30 minutes (I finally just minimized the window to wait it out) before the program allowed me to go back into the model to make the changes.  Is this normal?

--Scott

[sgold]

Need to clarify I realized.  I was using Simulation Flow 360.

[Inv_kaos]

Cancel the process through task manager. They run separate to AlgFrame.exe so you will just return to the graphical interface.

I don't know why these processes take so long, I would expect it to be instant but it is similar in SolidWorks too. Would be good if someone from Autodesk could shed some light on this.

[S.LI]

I'm not sure about Flow 360.

For Mechanical and Multiphysics, once a simulation is started, it goes into pre-processors and then processor(solver). No matter which stages it is at, we don't intend to kill a running code, since this would cause some data damage. So usually only a flag is set after a cancel signal is received. Code is going to check this flag at a moment when is safe to itself. So this Cancel only means a signal, instead of immediate reaction. In some specific case, this could take 20 minutes, or even longer.

Of course, to kill it in task manager is an option, but it might cause model damage.