|
[Sponsors] |
![]() |
![]() |
#1 |
New Member
Join Date: Oct 2023
Posts: 3
Rep Power: 2 ![]() |
I am Meshing a High Aspect Ratio Cooling Channel for a Conjugated Heat Transfer Simulation in Fluent. I created the geometry in Discovery and did a Share Topology for the shared surfaces. In ICEM, I set the edge parameters without using the refinement tool at first so that the solid and fluid blocks have the same number of nodes. But when I try using the Refinement tool, the generated Mesh shows errors of Uncovered Face in the solid zone cells adjacent to the Fluid Zone. Do not understand why this is happening? Have done this plenty of times before without having this error
|
|
![]() |
![]() |
![]() |
![]() |
#2 |
Senior Member
Marcin
Join Date: May 2014
Location: Poland, Swiebodzin
Posts: 313
Rep Power: 13 ![]() |
The "Uncovered Face" error in your solid zone cells adjacent to the fluid zone indicates a mesh incompatibility issue. Here's why it might be happening and how to address it:
**Understanding the Problem:** * **Mesh Mismatch:** When you set the edge parameters for both solid and fluid zones to have the same number of nodes initially, it might not translate perfectly when applying refinement with the tool. This can lead to slight discrepancies in mesh size and topology at the interface. * **"Uncovered Face" Error:** ICEM detects that some faces on the solid zone bordering the fluid zone are not entirely covered by the refined fluid mesh. This creates a discontinuity at the interface, which can cause problems in conjugated heat transfer simulations. **Solutions:** 1. **Refine Both Zones Simultaneously:** * Instead of setting the same number of nodes initially, consider applying refinement to both solid and fluid zones simultaneously using the refinement tool. * This ensures the mesh on both sides adapts together and maintains compatibility at the interface. 2. **Adjust Refinement Settings:** * If simultaneous refinement is not ideal, try adjusting the refinement settings. * Use a "Ratio" based refinement instead of a fixed number of elements. This allows for a more gradual transition between the solid and fluid zones. 3. **Check Shared Topology:** * Double-check that the "Share Topology" function in Discovery transferred the interface surfaces correctly to ICEM. * Any inconsistencies in the shared topology can lead to mesh incompatibility issues. 4. **Manual Mesh Matching:** * As a last resort, you can attempt manual mesh matching at the interface. * This involves adjusting the mesh on the solid zone to better align with the refined fluid mesh. However, this is a time-consuming and error-prone approach. **Additional Tips:** * **Preview Mesh:** Utilize the preview mesh option in ICEM before committing to the final mesh generation. This allows you to visualize potential issues like uncovered faces beforehand. * **Consult Documentation:** Refer to the ICEM documentation for specific details on the refinement tool and troubleshooting mesh incompatibility problems. By trying these solutions and refining your approach, you should be able to eliminate the "Uncovered Face" error and achieve a consistent mesh for your conjugated heat transfer simulation in Fluent. Remember, maintaining a compatible mesh between the solid and fluid zones is crucial for accurate results.
__________________
Quick Tips and Tricks, Tutorials FLuent/ CFX (CFD) https://howtooansys.blogspot.com/ |
|
![]() |
![]() |
![]() |
|
|
![]() |
||||
Thread | Thread Starter | Forum | Replies | Last Post |
Foam::error::PrintStack | almir | OpenFOAM Running, Solving & CFD | 92 | May 21, 2024 07:56 |
[snappyHexMesh] No generation of layer onto zerothickness surface | crubio.abujas | OpenFOAM Meshing & Mesh Conversion | 3 | October 25, 2022 03:20 |
[snappyHexMesh] Layers not growing at all | zonda | OpenFOAM Meshing & Mesh Conversion | 12 | June 6, 2020 11:28 |
[snappyHexMesh] SnappyHexMesh for internal Flow | vishwa | OpenFOAM Meshing & Mesh Conversion | 24 | June 27, 2016 08:54 |
[snappyHexMesh] snappyHexMesh won't work - zeros everywhere! | sc298 | OpenFOAM Meshing & Mesh Conversion | 2 | March 27, 2011 21:11 |