|
|
incorrect_cell.png (10,004 bytes) |
|
|
My issue looks very similar to http://www.openfoam.org/mantisbt/view.php?id=1493, but it wasn't solved yet. Like it is written in this issue, the problems with Courant number occures in this cells, so it is impossible to get a solution in a reasonable amount of time. Can anyone fix this bug in snap stage ?? |
|
|
snappyHexMesh creates the mesh you ask it to, obeying the mesh quality constraints. If you use put your mesh quality constraints in a system/meshQualityDict (see e.g. ./incompressible/simpleFoam/motorBike/system/meshQualityDict) you can run checkMesh -meshQuality and check the mesh against these constraints outside of snappyHexMesh. Other things to check - did you write the mesh in binary - what constraint gets rid of your problematic cells |
|
|
First of all I've checked my stl surface and found some self-intersections. I repaired this and start the snappyHexMesh ones again. But suddenly I've got even worst result that it was before. There are some holes in the surface (look at the picture above). As you advised me, I've checked my mesh with checkMesh -meshQuality and it says OK. But if I run snappyHexMesh -checkGeometry I've got an error like: "Checking for triangle quality. flange : has 746 bad quality triangles (quality < 0.01)" So it looks very strange because surfaceCheck on stl surface doesn't show me any kind of error. If I simply run snappyHexMesh the mesh is created witout any type of error. Looks very strange... The test case is available here: https://yadi.sk/d/Q-8Xg8NsfxyvP |
|
|
mesh_with_holes.png (154,362 bytes) |
|
|
Hello, Im not an expert in this field. But I downloaded your case in the first link. Be default in paraFoam, U will find some holes in your mesh. You can neglect these holes. Also in this way it will look better: 1. select Use VTKpolyhedron 2. Do Not select the internal mesh, just select the patch. I do this for your case, I think its good. |
- Anonymous
