|
[Sponsors] |
March 15, 2011, 02:40 |
snappyHexMesh Issue
|
#1 |
New Member
Thomas Walsh
Join Date: Nov 2010
Posts: 18
Rep Power: 15 |
I have been running into a strange issue with snappyHexMesh. Everytime I try to mesh a certain region with the 'snap' feature selected part of my geometry disappears. The part that disappears is a long narrow section. Curious if anyone else has come across this? The only way I have found to fix this issue is to increase the level of refinement very high. I have posted two picture below. The first shows the mesh with 'snap' turn off and the second with 'snap' turn on. Every other setting is the exact same.
|
|
March 15, 2011, 06:17 |
|
#2 |
Member
Dan
Join Date: Oct 2010
Location: UK
Posts: 41
Rep Power: 16 |
I think I'm running into a similar problem.
I have three .stl files that I exported from a single geometry in Salome, two of them seem to work properly with snappyHexMesh however the third seems to destroy the background mesh. so that it becomes the only patch with any faces. I think that for some reason snappyHexMesh is meshing inside the object instead of outside. Does anyone know a way of switching between internal and external boundary mode for a given solid? Dandalf |
|
March 15, 2011, 10:29 |
|
#3 |
Member
Dan
Join Date: Oct 2010
Location: UK
Posts: 41
Rep Power: 16 |
After a frustrating morning I managed to sort out my problem,
I had the location in mesh set to, locationInMesh (0 0 0); Which evidently was coincidental with an edge I stuch in some random numbers and the problem was fixed! |
|
March 15, 2011, 14:49 |
More Pics
|
#4 |
New Member
Thomas Walsh
Join Date: Nov 2010
Posts: 18
Rep Power: 15 |
Just for fun I meshed the exterior of my geometry and it seems to work fine with the 'snap' feature selected. I have posted two more pictures. The first shows this exterior mesh with the narrow channel in question on the left. The second picture shows the interior mesh without this channel. Only the location in mesh point was changed. Can anyone explain why this is happening? Do I need more cells to define this narrow channel? As can be seen the current refinement (2) only produces 1 cell width here. It was my understanding that the snap feature had no impact on the castellatedMesh process, but it seems I am wrong.
|
|
|
|
Similar Threads | ||||
Thread | Thread Starter | Forum | Replies | Last Post |
snappyHexMesh in parallel leads to segmentation fault | ChrisHa | OpenFOAM Pre-Processing | 1 | January 14, 2019 11:04 |
[snappyHexMesh] Running snappyHexMesh in parallel - optimizing | peterhess | OpenFOAM Meshing & Mesh Conversion | 2 | January 3, 2018 03:54 |
[snappyHexMesh] Tutorial crashes: snappyHexMesh floating point exception. | jasv | OpenFOAM Meshing & Mesh Conversion | 4 | May 10, 2016 03:55 |
[snappyHexMesh] snappyhexmesh doesn't creat mesh in parallel issue? | klausb | OpenFOAM Meshing & Mesh Conversion | 1 | March 7, 2015 12:55 |
[snappyHexMesh] SnappyHexMesh not generate mesh first time | mavimo | OpenFOAM Meshing & Mesh Conversion | 4 | August 26, 2008 08:08 |