|
[Sponsors] |
December 7, 2020, 00:52 |
Mesh has uncovered edges
|
#1 |
New Member
Join Date: Nov 2020
Posts: 23
Rep Power: 5 |
Hi,
I have created a mesh for a nozzle, after pre-mesh when I try to convert it into a .msh file, I face the following error: WARNING: Mesh has uncovered faces. Done WARNING: Mesh has uncovered edges. ANSYS Fluent needs a complete boundary (lines in 2D) or it will give a variety of errors and not read in the mesh! If this was 2D Hexa, perhaps your edges are not associated with perimeter curves. I have tried some of the suggestions in similar posts but I'm unable to solve the problem. I'll appreciate your help. |
|
December 7, 2020, 02:06 |
|
#2 |
Senior Member
Kira
Join Date: Nov 2020
Location: Canada
Posts: 435
Rep Power: 8 |
Hello Saadia,
It sounds like and looks like you used a structured mesh. When you were blocking the object did you do so with a 2D (i.e. 2D planar surface) or a 3D option? In 2D, the error means you really have "uncovered edges" around your shells. This means the solver has nowhere to put the boundary conditions and that is a problem. The fix is simple enough... When using ICEM CFD Hexa for 2D blocking ALWAYS associate the perimeter edges to the curves... When you do that, you will get the perimeter line elements that your solver needs. After doing this, regenerate the mesh and the problem should be fixed. If it is not, there is also the option in ICEM to fix uncovered faces. Go to edit mesh-->check mesh--> check and fix uncovered faces |
|
December 7, 2020, 02:57 |
|
#3 |
New Member
Join Date: Nov 2020
Posts: 23
Rep Power: 5 |
I have used a 2D planar surface and associated edges to the curves but still, this error appeared again. When I deselect the geometry and select the Mesh lines only, I see no error between the lines and geometry.
I have tried the ICEM edit mesh option too, but nothing seems to work for me. |
|
December 7, 2020, 10:03 |
|
#4 |
Senior Member
Sebastian Engel
Join Date: Jun 2011
Location: Germany
Posts: 566
Rep Power: 21 |
Check the black-colored edge in the outlet region. This is has likely the wrong (default) to-surface association. Just delete the association to make it internal again
|
|
December 7, 2020, 21:51 |
|
#5 |
New Member
Join Date: Nov 2020
Posts: 23
Rep Power: 5 |
It worked. Thank you. The .msh file was generated but when I load the mesh file into Fluent, it gives me an error "Error Inquire-adjacent-threads: not a face thread". Any suggestion?
|
|
December 9, 2020, 21:17 |
|
#6 |
Senior Member
Sebastian Engel
Join Date: Jun 2011
Location: Germany
Posts: 566
Rep Power: 21 |
I never encountered this error before.
There is literally only one post if you search for "inquire adjacent threads".... I suggest:make it your default behavior to smash error message into search engines, prefer the most unique words in a string. Sometimes google has a better index for this forum than this forum's backend. Anyhow: Inquire adjacent threads error No idea whether it's any help to you, but a few users showed positive feedback. Best, Sebastian |
|
|
|
Similar Threads | ||||
Thread | Thread Starter | Forum | Replies | Last Post |
[snappyHexMesh] Add Mesh Layers doesnt work on the whole surface | Kryo | OpenFOAM Meshing & Mesh Conversion | 13 | February 17, 2022 07:34 |
[snappyHexMesh] Snappy Hex Mesh - issue with smoothness of the model edges | olek.warc | OpenFOAM Meshing & Mesh Conversion | 1 | August 31, 2018 11:31 |
[snappyHexMesh] SnappyHexMesh for internal Flow | vishwa | OpenFOAM Meshing & Mesh Conversion | 24 | June 27, 2016 08:54 |
Convergence moving mesh | lr103476 | OpenFOAM Running, Solving & CFD | 30 | November 19, 2007 14:09 |