|
[Sponsors] |
[snappyHexMesh] Trouble with stl file: surface not closed (snappyHexMesh) |
|
LinkBack | Thread Tools | Search this Thread | Display Modes |
April 2, 2011, 07:04 |
Trouble with stl file: surface not closed (snappyHexMesh)
|
#1 |
New Member
Join Date: Mar 2009
Posts: 15
Rep Power: 17 |
Hi all,
I'm trying to create a mesh for internal flow inside a pump intake sump. I created a simplified geometry in SolidWorks and saved it as a .stl file. A picture of the geometry is attached. It consists of an open-top rectangular box representing the sump walls, covered at the top with a plane where I plan to have a patch representing the water level. An outlet pipe is partially submerged into the sump, and there is a rectangular opening at the bottom of the sump on one side representing an inlet. I've added plane lids at the inlet and pipe outlet to close the geometry and to create patches for defining the necessary boundary conditions. The problem I have is that, even though I specify a location inside the sump for meshing in snappyHexMeshDict, cells from the background mesh outside the target domain do not get removed. When I checked with surfaceCheck (log file attached), it says that the geometry is not closed. I am not sure what I am doing wrong since the lids on the inlet and outlet should ensure that the geometry is closed. I've also attached the (compressed) stl file for reference. Any help or advice is highly appreciated. Thanks |
|
April 2, 2011, 08:13 |
|
#2 | |
Retired Super Moderator
Bruno Santos
Join Date: Mar 2009
Location: Lisbon, Portugal
Posts: 10,982
Blog Entries: 45
Rep Power: 128 |
Greetings sfalsharif,
I saw a thread about such a problem almost a year ago and here is the solution: Quote:
Bruno
__________________
|
||
April 2, 2011, 18:18 |
|
#3 |
New Member
Join Date: Mar 2009
Posts: 15
Rep Power: 17 |
Hi Bruno,
Thanks for bringing AdMesh to my attention, it looks like something that might come in handy some time. Unfortunately, in this case it has not solved my problem. Apparently it added some facets, but surfaceCheck still says the resulting surface is open for some reason. I still have cells from the background mesh outside my desired computational domain. I wonder if SolidWorks is a good choice for creating stl files for this purpose? Should I try something else? What I plan to test tomorrow is to create a single part blind hollow box stl and try meshing that, just to see if the rest of the steps (e.g. snappyHexMeshDict) are OK. Any further suggestions are welcome Regards, Sharaf Last edited by sfalsharif; April 2, 2011 at 18:19. Reason: typo |
|
April 3, 2011, 06:53 |
|
#4 |
Retired Super Moderator
Bruno Santos
Join Date: Mar 2009
Location: Lisbon, Portugal
Posts: 10,982
Blog Entries: 45
Rep Power: 128 |
Hi Sharaf,
I've just visually checked the STL you posted and it seems the lid for the tube was STL'ized as an independent surface, which lead to various small holes due to the unconnected vertices between the lids and the interior tube wall. I would test generating this geometry without the tube and see how it behaves. Then on another test simply add the hole with lid where the tube goes in; this test should reveal the same bug as the original lid+tube. The other test possibility would be to change the lid to a bigger slate that covers the tube completely, like cutting it through. Other things to test would be forcing the lid to be attached to the tube in SolidWorks, if possible. Another would be increasing the export STL resolution. I know that 3D CAD in SolidWorks and any other similar programs always have these kinds of quirks and kinks. What looks good on paper, still needs very detailed work on the 3D geometries for CFD and FEM simulations. If you don't properly define relations between objects, the export processes will always leave out important details that you didn't include in the first place! Best regards, Bruno
__________________
|
|
Tags |
mesh, snappyhexmesh, solidworks |
|
|
Similar Threads | ||||
Thread | Thread Starter | Forum | Replies | Last Post |
[Other] Tabulated thermophysicalProperties library | chriss85 | OpenFOAM Community Contributions | 62 | October 2, 2022 04:50 |
how to calculate mass flow rate on patches and summation of that during the run? | immortality | OpenFOAM Post-Processing | 104 | February 16, 2021 09:46 |
[Other] Adding solvers from DensityBasedTurbo to foam-extend 3.0 | Seroga | OpenFOAM Community Contributions | 9 | June 12, 2015 18:18 |
friction forces icoFoam | ofslcm | OpenFOAM | 3 | April 7, 2012 11:57 |
OpenFOAM on MinGW crosscompiler hosted on Linux | allenzhao | OpenFOAM Installation | 127 | January 30, 2009 20:08 |