|
[Sponsors] |
[cfMesh] Surface topology (wanted: ok (non-closed singly connected), is: ok (empty)) ??? |
|
LinkBack | Thread Tools | Search this Thread | Display Modes |
March 29, 2018, 08:11 |
Surface topology (wanted: ok (non-closed singly connected), is: ok (empty)) ???
|
#1 |
New Member
Helene
Join Date: Mar 2018
Location: Karlsruhe
Posts: 3
Rep Power: 8 |
Hi:
I have a problem generating a mesh with cfMesh. I am working on a stirrer for my thesis, and I differentiate between rotor (rotating part) and stator. The mesh of the stator is ready and functional. Only with the generation of the mesh for the rotor I have problems. The approach is identical: With the help of the software Salome I determined the later patches and transferred them into the stl file format. With surfaceFeatureEdges constant/triSurface/rotor.stl constant/triSurface/rotor.fms I convert the stl files to fms files. Then I start meshing. cartesianMesh While all patches are detected with the stator, this is not the case with the rotor. I get the following message in the checkMesh log-file: Checking patch topology for multiply connected surfaces... Patch Faces Points Surface topology impellerblades 0 0 ok (empty) impellerdisk 90 102 ok (non-closed singly connected) impellershaft 166 173 ok (non-closed singly connected) interface 634 659 ok (non-closed singly connected) tankbottomrot 0 0 ok (empty) tanktoprot 92 100 ok (non-closed singly connected) The patches 'impellerblades' and 'tankbottomrot' are 'empty'... I have also checked the log file of carthesianMesh. It says, among other things: Found 4 problematic vertices Found 2 non-mappable cells Found 8 points with inverted surface normals. With the help of a script I connected the individual stl files and checked the vectors (foudn here: http://openfoamwiki.net/index.php/Th...arametrization). In addition, I reconstructed the geometry of the rotor in salome. In constant/boundaries all patches are declared as wall as intended. Also in paraview I was able to have a look at the surfaces. To be sure, I also transferred the patches to ansii by using paraview (I saw this hint in a forum). I just don't know what to do. Do you have any ideas? I do not understand my mistake. Kind regards, Helene Last edited by Helene; April 19, 2018 at 06:51. |
|
April 19, 2018, 06:49 |
Fixed
|
#2 |
New Member
Helene
Join Date: Mar 2018
Location: Karlsruhe
Posts: 3
Rep Power: 8 |
Hello,
I fixed the problem myself. I had set the mesh of cfMesh to coarse and so the missing patches could not be visualized. By the local refinement of the mesh at those regions, my error could be fixed. Many greetings, Helene |
|
|
|
Similar Threads | ||||
Thread | Thread Starter | Forum | Replies | Last Post |
Simulating fire in a tunnel | luca1992 | OpenFOAM | 14 | August 16, 2017 13:50 |
[snappyHexMesh] sHM too many cells | Knapsack | OpenFOAM Meshing & Mesh Conversion | 2 | July 8, 2017 07:41 |
Tecplot 360 2011 R2 preview with OpenFOAM data loader available for evaluation | scott_rumage | OpenFOAM Post-Processing | 50 | January 23, 2017 02:49 |
snappyHexMesh - memory corruption (OF-v. 2.2.x) | pct | OpenFOAM Bugs | 9 | July 21, 2013 13:57 |
CFX4.3 -build analysis form | Chie Min | CFX | 5 | July 12, 2001 23:19 |