|
[Sponsors] |
December 8, 2024, 11:00 |
snappyHexMesh leading to checkMesh errors
|
#1 |
New Member
Elias Wahbah Makhoul
Join Date: Nov 2024
Posts: 1
Rep Power: 0 |
Hey, cfd and openfoam beginner here
I am using snappyHexMesh to cut out a triangular section off a block from blockmesh to construct a weir geometry. When I do not do any refinement at all in snappyHexMesh in surface and region refinement as well as in the features section, checkMesh determines my mesh is okay. But when i do any refinement even if it is a slight refinement, snappyHexmesh takes a long time to run and it gives me the following warning: Correcting 2-D mesh motion--> FOAM Warning : From void Foam::twoDPointCorrector::calcAddressing() const in file twoDPointCorrector/twoDPointCorrector.C at line 163 The number of points in the mesh is not equal to twice the number of edges normal to the plane - this may be OK only for wedge geometries. Please check the geometry or adjust the orthogonality tolerance. Number of normal edges: 72380 number of points: 108570 To be honest i do not really know what this means, and how to not make the number of points in the mesh=2*number of edges normal to the plane checkMesh output after that is : Checking geometry... Overall domain bounding box (0 0 0) (7.43 2.49 0.1) Mesh has 2 geometric (non-empty/wedge) directions (1 1 0) Mesh has 2 solution (non-empty) directions (1 1 0) ***Number of edges not aligned with or perpendicular to non-empty directions: 428 <<Writing 856 points on non-aligned edges to set nonAlignedEdges Boundary openness (-8.28006e-18 -2.27867e-18 -1.86051e-15) OK. Max cell openness = 2.25296e-16 OK. Max aspect ratio = 7.11896 OK. Minimum face area = 0.000442183. Maximum face area = 0.00505375. Face area magnitudes OK. Min volume = 2.2111e-05. Max volume = 0.000118399. Total volume = 1.74157. Cell volumes OK. Mesh non-orthogonality Max: 63.788 average: 2.14428 Non-orthogonality check OK. Face pyramids OK. Max skewness = 3.33875 OK. Coupled point location match (average 0) OK. Failed 1 mesh checks. what i tried to do(these did not help): increase number of cells in blockmesh tried to improve snappyhexmesh parameetrs like resolvefeatureAngle and mesh quality parameters checked quality of stl geometry using surfaceCheck, it gave me that the stl is okay: Reading surface from "new_weir.stl" ... Statistics: Triangles : 8 in 1 region(s) Vertices : 6 Bounding Box : (0.897 8.67362e-19 0) (1.24 0.049 0.31) Region Size ------ ---- Mesh 8 Surface has no illegal triangles. Triangle quality (equilateral=1, collapsed=0): 0 .. 0.05 : 0 0.05 .. 0.1 : 0.25 0.1 .. 0.15 : 0 0.15 .. 0.2 : 0 0.2 .. 0.25 : 0 0.25 .. 0.3 : 0 0.3 .. 0.35 : 0 0.35 .. 0.4 : 0 0.4 .. 0.45 : 0 0.45 .. 0.5 : 0.25 0.5 .. 0.55 : 0 0.55 .. 0.6 : 0 0.6 .. 0.65 : 0 0.65 .. 0.7 : 0 0.7 .. 0.75 : 0 0.75 .. 0.8 : 0.5 0.8 .. 0.85 : 0 0.85 .. 0.9 : 0 0.9 .. 0.95 : 0 0.95 .. 1 : 0 min 0.0829016 for triangle 0 max 0.765878 for triangle 6 Edges: min 0.109567 for edge 1 points (0.897 8.67362e-19 0)(0.995 0.049 0) max 0.46233 for edge 11 points (0.897 8.67362e-19 0.31)(1.24 8.67362e-19 0) Checking for points less than 1e-6 of bounding box ((0.343 0.049 0.31) metre) apart. Found 0 nearby points. Surface is closed. All edges connected to two faces. Number of unconnected parts : 1 Number of zones (connected area with consistent normal) : 1 End please help me fix my problem so i can do refinement using snappyhexmesh |
|
Tags |
blockmesh, snappyhexmesh 2d, surfacecheck, weir |
|
|
Similar Threads | ||||
Thread | Thread Starter | Forum | Replies | Last Post |
chtMultiRegionFoam not writing any results but not giving any errors | lmw354 | OpenFOAM Running, Solving & CFD | 5 | August 29, 2021 04:04 |
AMI interDyMFoam for mixer nu problem | danny123 | OpenFOAM Programming & Development | 8 | September 6, 2013 03:34 |
Convergence moving mesh | lr103476 | OpenFOAM Running, Solving & CFD | 30 | November 19, 2007 15:09 |
IcoFoam parallel woes | msrinath80 | OpenFOAM Running, Solving & CFD | 9 | July 22, 2007 03:58 |
Could anybody help me see this error and give help | liugx212 | OpenFOAM Running, Solving & CFD | 3 | January 4, 2006 19:07 |