[snappyHexMesh] surfaceCheck detects all faces as problem faces

Seb_Ve · April 18, 2018, 03:51

Hello all,

I am trying to create a mesh using snappyHexMesh but I'm not really satisfied with the results. Therefore I used the surfaceCheck function to check the stl files I am using. And there are indeed problems with them because it says "surface is not closed because not all edges are connected to two faces". When I visualize the problemFaces in paraview with surfaceSubset function I get my original geometry. So it looks like the whole geometry has a flaw but I don't know why.

Did anyone have the same problem at some time and some help for me?

Greetings,
Sebastian

akidess · April 18, 2018, 04:48

Make a new, proper STL or try fixing it with the surfaceHookup utility.

Seb_Ve · April 18, 2018, 06:40

Thanks for your answer!

But what makes a proper Stl file? I exported it in relatively high resolution from ptc creo, parted it with blender in different parts like inlet, outlet etc. And further refined the stl mesh. What could I have done so that it‘s not a proper stl file?

Bdew8556 · May 6, 2019, 02:32

I'm having a similar problem to Seb.

All my geometry is connected, I know this because I set it up that way in Fusion 360. When I run surfaceCheck it says its not all connected, yet the simulation works ok?

quarkz · August 23, 2020, 10:43

Hi, I think you can try 3D builder in the windows store. It's a 1 click repair which works for my case. Note that your output may be shifted after that, if it lies in the negative coordinates.

April 18, 2018, 03:51	surfaceCheck detects all faces as problem faces	#1
Seb_Ve New Member Sebastian Vetter Join Date: Dec 2017 Posts: 9 Rep Power: 8	Hello all, I am trying to create a mesh using snappyHexMesh but I'm not really satisfied with the results. Therefore I used the surfaceCheck function to check the stl files I am using. And there are indeed problems with them because it says "surface is not closed because not all edges are connected to two faces". When I visualize the problemFaces in paraview with surfaceSubset function I get my original geometry. So it looks like the whole geometry has a flaw but I don't know why. Did anyone have the same problem at some time and some help for me? Greetings, Sebastian

April 18, 2018, 04:48		#2
akidess Senior Member Anton Kidess Join Date: May 2009 Location: Germany Posts: 1,377 Rep Power: 29	Make a new, proper STL or try fixing it with the surfaceHookup utility. __________________ On twitter @akidTwit Spend as much time formulating your questions as you expect people to spend on their answer.

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
[snappyHexMesh] Add Mesh Layers doesnt work on the whole surface	Kryo	OpenFOAM Meshing & Mesh Conversion	13	February 17, 2022 07:34
[snappyHexMesh] SHM is not extruding/adding Layers everywhere	matthiasd	OpenFOAM Meshing & Mesh Conversion	2	October 16, 2016 16:45
decomposePar -allRegions	stru	OpenFOAM Pre-Processing	2	August 25, 2015 03:58
SigFpe when running ANY application in parallel	Pj.	OpenFOAM Running, Solving & CFD	3	April 23, 2015 14:53
foam-extend_3.1 decompose and pyfoam warning	shipman	OpenFOAM	3	July 24, 2014 08:14

April 18, 2018, 06:40		#3
Seb_Ve New Member Sebastian Vetter Join Date: Dec 2017 Posts: 9 Rep Power: 8	Thanks for your answer! But what makes a proper Stl file? I exported it in relatively high resolution from ptc creo, parted it with blender in different parts like inlet, outlet etc. And further refined the stl mesh. What could I have done so that it‘s not a proper stl file?

May 6, 2019, 02:32		#4
Bdew8556 Senior Member Brett Join Date: May 2013 Posts: 212 Rep Power: 13	I'm having a similar problem to Seb. All my geometry is connected, I know this because I set it up that way in Fusion 360. When I run surfaceCheck it says its not all connected, yet the simulation works ok?

August 23, 2020, 10:43		#5
quarkz Senior Member TWB Join Date: Mar 2009 Posts: 400 Rep Power: 19	Hi, I think you can try 3D builder in the windows store. It's a 1 click repair which works for my case. Note that your output may be shifted after that, if it lies in the negative coordinates.