When i hit the Run Case button on the gui i got an error message that says: File “MFlow_MVRC.py”, line 1691, in run_case KeyError: ‘local_DockerToolbox’ Maybe i’m missing something but i couldnt find what so decieded to ask it away.
Did you enter the correct path in the MantiumFlow configuration file?
When using the GUI you can find it by clicking the MantiumCAE logo in the lower right corner and then on configuration.
Can you explain me the commands? I didnt use any commands since the gui came out for the previous software so apperantly i forgot the dos commands.
Hm, I not really sure how to do it in Windows either. Maybe someone else can help. You could try using the old GUI just to see if that one will do the trick of starting the simulation.
But I would assume that the Windows OF version has some kind of command prompt. If it does open it, head over to your case and execute the runCase script.
I tried to look into but I can’t get into the settings page.
Only the Apply button before opening a case.
Nothing after opening the case.
W10
Well somehow i managed to escalade the problem and corrupt my openfoam. I downloaded and tried both 1612+ and 1606+ but after running the OF_Env_Create as administrator, virtual box doesnt run the default virtual machine and gives error codes like this:
Failed to open a session for the virtual machine default.The VM session was aborted.Result Code: E_FAIL (0x80004005)Component: SessionMachineInterface: ISession {7844aa05-b02e-4cdd-a04f-ade4a762e6b7}
Status update:
After trying the samething over and over like a mad man, i fixed the openfoam errors but unfortunately the new software still gives that ” KeyError: ’local_DockerToolbox’ ” error
You should definitively be using OF v1606+. The newer version will not work as many post-processing related things have changed. Try to uninstall everything and then follow these instructions:
https://mantiumchallenge.com/installation-instructions-install-openfoam-v1606-windows/
I managed to get the 1606+ working but as i said, new software still gives the same error.