[snappyHexMesh] Two different layer thicknesses with same settings

Tobi · October 25, 2012, 07:10

Hello Foamers,

I meshed a case with layers today:

Code:

castellated      true;
snap                true;
addLayers       true;

and realized that there was no layer adding. The output of the layer hight was:

Code:

patch  faces    layers avg thickness[m]
                       near-wall overall
-----  -----    ------ --------- -------
WallBC 36807    4      6.9e-07   4.27e-06

In that case there are no adding layer. I switched off castellated and snap option and tried the layer adding again. Now successfully!
The output therefor is:

Code:

patch  faces    layers avg thickness[m]
                       near-wall overall
-----  -----    ------ --------- -------
WallBC 36807    4      0.000333  0.00206

The question
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Why is snappyHexMesh calculating two different thicknesses with the same settings?

Can someone give me an advice?
Thanks in advance

Tobi

Tobi · October 25, 2012, 08:04

Hi all,

the problem is caused by salome.
The UNV mesh is destroyed or something like that if you export it and convert it into a foam mesh. There are some problems with unused points.

After building the same backgroundmesh in a other way. It works now.

Solved!

October 25, 2012, 07:10	Two different layer thicknesses with same settings	#1
Tobi Super Moderator Tobias Holzmann Join Date: Oct 2010 Location: Tussenhausen Posts: 2,708 Blog Entries: 6 Rep Power: 51	Hello Foamers, I meshed a case with layers today: Code: castellated true; snap true; addLayers true; and realized that there was no layer adding. The output of the layer hight was: Code: patch faces layers avg thickness[m] near-wall overall ----- ----- ------ --------- ------- WallBC 36807 4 6.9e-07 4.27e-06 In that case there are no adding layer. I switched off castellated and snap option and tried the layer adding again. Now successfully! The output therefor is: Code: patch faces layers avg thickness[m] near-wall overall ----- ----- ------ --------- ------- WallBC 36807 4 0.000333 0.00206 The question - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Why is snappyHexMesh calculating two different thicknesses with the same settings? Can someone give me an advice? Thanks in advance Tobi

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
[snappyHexMesh] snappyHexMesh Boundary Layer at Corner	panpanzhong	OpenFOAM Meshing & Mesh Conversion	5	July 3, 2018 05:53
[snappyHexMesh] SnappyHexMesh: Layer on corners	Pj.	OpenFOAM Meshing & Mesh Conversion	9	July 17, 2014 04:26
[snappyHexMesh] Layers:problem with curvature	giulio.topazio	OpenFOAM Meshing & Mesh Conversion	10	August 22, 2012 09:03
[snappyHexMesh] Layers don't fully surround surface	EVBUCF	OpenFOAM Meshing & Mesh Conversion	14	August 20, 2012 04:31
Questions about Boundary Layer Thickness and Turbulence Models	famerfamer	STAR-CCM+	3	July 12, 2012 09:47

October 25, 2012, 08:04		#2
Tobi Super Moderator Tobias Holzmann Join Date: Oct 2010 Location: Tussenhausen Posts: 2,708 Blog Entries: 6 Rep Power: 51	Hi all, the problem is caused by salome. The UNV mesh is destroyed or something like that if you export it and convert it into a foam mesh. There are some problems with unused points. After building the same backgroundmesh in a other way. It works now. Solved!