|
[Sponsors] |
June 2, 2016, 00:07 |
Empty Surfaces_help
|
#1 |
New Member
|
Hello CFD enthusiasts.
For my Honours thesis this year I am conducting CFD simulations using ANSYS Fluent in Workbench. Currently I have encountered some difficulties with empty surfaces and zones being created when my meshed model is imported into Fluent from Meshing, as seen in Zonesurface.PNG. Referring to Console.PNG, the last three zones were note created by me and appear when the model is first opened in Fluent. Attached is a capture of the meshed model in Fluent for reference if needed. I will also note this is my first post on CFD-Online. It would really be appreciated if someone could help me mitigate this problem. I am aware I can delete the Surfaces in Fluent through the Zone surface management. Please let me know if you can help. Thanks in advance Thomas Kinney |
|
June 2, 2016, 04:44 |
|
#2 |
Senior Member
Join Date: Nov 2013
Posts: 1,965
Rep Power: 26 |
Those empty walls come from your interface.
You have an interface (or 'contact' in workbench-terms) between "fluidinterface" and "airinterface". In general, when you make an interface between to surfaces, some cells might match and some cells might not match. Suppose for simplicity that your two surfaces are like this: Code:
airinterface +----------------+ +----------------+ fluidinterface A: cells on the side of 'airinterface' that match cells from 'fluidinterface'. B: cells on the side of 'airinterface' that don't match cells from 'fluidinterface'. C: cells on the side of 'fluidinterface' that match cells from 'airinterface'. D: cells on the side of 'fluidinterface' that don't match cells from 'airinterface'. Code:
B A +---|------------+ +------------|---+ C D Types B and D are the bad ones. In your case, Fluent puts them in the zones "wall-18" and "wall-19". It looks like that as of Fluent 17, the names of these zones are more descriptive of what they are, they would have been something like "airinterface-contact_region_wall_src" or so. Fluent is a bit annoying with these zones ("wall-18"):
My way to deal with them: if you know your interfaces are good so these zones should be small or empty, ignore them. Only exception: if you are doing particle simulations, and these 'empty walls' are set to trap particles, and particles are reported as being 'trapped' on these empty walls, you need to know which interface they are associated with if you want to know how to do statistics with these particles. |
|
|
|
Similar Threads | ||||
Thread | Thread Starter | Forum | Replies | Last Post |
parasitic currents | rcastilla | OpenFOAM Programming & Development | 135 | November 29, 2017 10:53 |
[mesh manipulation] Importing Multiple Meshes | thomasnwalshiii | OpenFOAM Meshing & Mesh Conversion | 18 | December 19, 2015 18:57 |
[snappyHexMesh] sHM quality of multi-region | aminem | OpenFOAM Meshing & Mesh Conversion | 0 | April 16, 2015 11:38 |
Instable natural convection case | Peter88 | OpenFOAM | 5 | August 18, 2011 01:23 |
How to model the NR eqns in a domain with empty space | Vasilis | Main CFD Forum | 1 | April 14, 2009 04:35 |