🎉Community Raffle - Win $25

An exclusive raffle opportunity for active members like you! Complete your profile, answer questions and get your first accepted badge to enter the raffle.

Join and Win

Is there a way to interrupt a command in Flux?

Altair Forum User

Hello,

with bigger models I had the problem recently, that some commands were taking a lot of time (from several minutes to even hours) to complete. These commands could be meshing the domain, assembling objects etc. Is there a way to interrupt the ongoing command and return to the previous step?

I tried the STOP sign during meshing. But that does not work if the mesher is in the state of repairing the mesh.

My work around is to save beforehand, execute the command and if it takes too long or the output messages show problems, I kill the whole Flux process.

Find more posts tagged with

English

Flux

Accepted answers

All comments

Alejandro Rodríguez

Hello.

Unfortunately, the commands are treated one by one, so a new command cannot be run until the previous one was finished, this remains true if the commands is introduced through the GUI or a python instruction/file.

In conclusion, you cannot choose to stop a command depending on how much time he spends to finish.

Best regards.

Altair Forum User

Thank you for your answer. Though it's not what I wanted to hear.

Maybe this could be added as an improvement for a coming release? This could be very helpful, especially for longer or more complex operations. So one could send the interrupt and change the settings before starting the command again.

Kind regards.

Alejandro Rodríguez

You are welcome.

In fact, this is a good possibility for a “new feature request”.

Today, your best option if one commands takes a long time is to kill your Flux project manually and take advantage of the automatically generated python file to reproduce all the non-blocking steps that have been done after the last project opening. You will find this python file in your working directory under the name Flux2D_log.py (or Flux3D_log.py). Of course, you can edit it as any usual Python file, it is also worthwile to notice that only the finish commands are recorded there (i.e., the blocking command will not be there).

Best regards.