In the past year,I learned very much from Ladybug discourse forum. Thank you for everyone.
When I am using Butterfly,sometimes I did some incorrect setting and start the running then. I wanted to save the result and stop the OpenFOAM running. I try to shutdown the command windows of OpenFOAM,but the result is not saved.
Is there any method or function component can save the result and stop the openfoam running?
Unless it’s an optimization study the Grasshopper interfaces stays interactive while you’re running Butterfly solution. You can set up the write Interval to 1 which will make OpenFOAM to save the results for each iteration and once the results is saved you can stop the solution. Also a clean way to do that is to set _run to False instead of closing the cmd window. I have seen cases that closing the cmd doesn’t stop the job in the background in VM.
I’ve stumbled in a similar situation and was wondering:
If I stop a decomposed simulation (on 10 cores) prematurely, would I have to reconstruct the solution manually in OpenFOAM or is Butterfly smart enough to do so automatically?
Hi @minggangyin thank you for your quick and helpful reply!
Unfortunately, I am not very experienced with OpenFOAM yet, could you point me out, where and how I’d execute this command? Would I do it with blueCFD?
It’s not possible directly from the GH/Butterfly interface, right?
Edit: I just discovered, that it is possible to change the case type in ParaView to “Decomposed”, which already kind of helps.
Following @minggangyin 's comments, indeed you can write a case using butterfly and then execute commands in the BlueCFD terminal.
Here are the usual commands I execute manually in the terminal. (XX is the number of processors)