su2 would not start iterating
 

Hi,

I'm trying to run a 3D incompressible eulers simulation using SU2 (Version 7.5.0 "Blackbird"),

the case is basically an umbrella canopy embedded in a simple box mesh, subjected to 8m/s freestream.

The solver simply won't start iterating, it does not print any error message but I think the problem could be:

"WARNING: SURFACE_PRESSURE_DROP can only be computed for at least 2 surfaces (outlet, inlet, ...)"

Any help would be appreciated.

That is not the issue. Can you upload your config? Or reproduce the problem with a smaller mesh? (check your system monitor maybe you are running out of memory)
Are you running with MPI? On linux or windows? etc. etc. more detail please :)

OK will do. I'm on Windows, not running any parallelism, just a single computer.
Here's my config and .geo file, (.su2 mesh too large to upload)
The config file I'm using is basically the one in the incompressible hydrofoil tutorial, left it mostly unchanged because I just wanted to test things. (This is my first CFD experience)
And I made my mesh with Gmsh.

Thanks. :)

Do the SU2 tutorial cases run for you?

I tried it now, opened the geo in gmsh, clicked 3D Mesh and exported as SU2 (do not select export all elements).
The solver started fine, it uses about 3.2GB of RAM so that's probably not the issue.
I don't know much about running SU2 on windows but check if you are not on a system folder (or protected some other way).
If you open task manager is SU2 using any CPU while it is stuck?

Yes they all work, tutorials and test cases

Still can't get the solver to start.
It's definitely not an memory issue, I've tried smaller meshes, same problem.

It doesn't seem su2 uses any CPU while it's stuck :/

All my executables are in C:\CFD\bin\SU2, and I created sub directories in CFD for all my runs

I just tried it on a Mac, same problem (Please see attached pics)
Any idea where I screwed up? :(
Many thanks for all your help.

I noted this time the command line does print
"segmentation fault: 11"
at the end,

So this could be a security related problem the whole time?