[snappyHexMesh] locationInMesh not working?

mattkoch · September 17, 2016, 01:31

Hello,

I have spent fairly massive amounts of time trying to understand blockMesh and snappyHexMesh. I am trying to mesh the interior of a performance theatre for air flow calculations. Attached are the STL, blockMeshDict and and snappyHexMeshDict files of a highly simplified version. Also attached is the Model.hdf file for Salome, where I created the original model and STL files.

I am fairly certain that my locationInMesh is pointing to the interior, but when I run this case using simple blockMesh and snappyhexMesh commands (no other arguments), my mesh shows BOTH the interior AND exterior regions on paraFoam. I must be doing something wrong, but what?

Thanks,

Matt Koch

mattkoch · September 17, 2016, 15:45

So, I woke up this morning thinking "Didn't I read about STL quality problems somewhere when learning about snappyHexMesh?". I did a quick web search, and sure enough I found that using Salome STL files generated from its GEOMETRY module are of very poor quality. Instead, it was recommended to generate STL files from Salome's MESH module. So, I generated surface meshes there and exported these. Low and behold, that seems to have led to success, at least for the case I posted yesterday. The new STL files are much too big to attach, though.

CFDUser29 · July 9, 2023, 14:11

Hello,
I wonder if you had any problem with your mesh with the complex version of your theatre? I am working on a ship, and there is the mesh inside the ship that is not deleting, though using locationsOutsideMesh and locationInMesh.
The ship and domain are built on Rhinocéros 3D, exported as .obj and converted as .stl files with Blender which seems recommended for OpenFoam.
I am also using snappyHexMesh.
Hope you can answer me or anyone else.

September 17, 2016, 15:45	probably an STL problem!	#2
mattkoch New Member Matt Koch Join Date: Sep 2016 Posts: 2 Rep Power: 0	So, I woke up this morning thinking "Didn't I read about STL quality problems somewhere when learning about snappyHexMesh?". I did a quick web search, and sure enough I found that using Salome STL files generated from its GEOMETRY module are of very poor quality. Instead, it was recommended to generate STL files from Salome's MESH module. So, I generated surface meshes there and exported these. Low and behold, that seems to have led to success, at least for the case I posted yesterday. The new STL files are much too big to attach, though.

Thread Tools	Search this Thread
Show Printable Version Email this Page	Search this Thread: Advanced Search
Display Modes
Linear Mode Switch to Hybrid Mode Switch to Threaded Mode

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
findCell() in parallel: not working if location is outside the domain	TobiWol	OpenFOAM	0	January 10, 2018 14:33
Processor 0 not working	vishwesh	OpenFOAM Running, Solving & CFD	0	November 17, 2017 03:35
Is the subsetMotionSolver working in parallel?	Arnoldinho	OpenFOAM Running, Solving & CFD	7	April 27, 2016 04:38
DPM parallel is not working but serial is working	johnwinter	FLUENT	1	March 27, 2012 02:01
Working directory	mgonzalo	FLUENT	1	November 11, 2011 10:05

July 9, 2023, 14:11		#3
CFDUser29 New Member Join Date: Jun 2023 Location: Brest Posts: 21 Rep Power: 2	Hello, I wonder if you had any problem with your mesh with the complex version of your theatre? I am working on a ship, and there is the mesh inside the ship that is not deleting, though using locationsOutsideMesh and locationInMesh. The ship and domain are built on Rhinocéros 3D, exported as .obj and converted as .stl files with Blender which seems recommended for OpenFoam. I am also using snappyHexMesh. Hope you can answer me or anyone else.