Fluent MESH check

Diger · July 13, 2016, 10:56

What does it mean when I check the quality of the mesh within fluent and it tells me:
Checking mesh........................
WARNING: Unassigned interface zone detected for interface 10............
Done.

WARNING: Mesh check failed.

To get more detailed information about the mesh check failure
increase the mesh check verbosity via the TUI command
/mesh/check-verbosity.

Diger · July 13, 2016, 15:42

And where exactly am I supposed to type this TUI command
/mesh/check-verbosity
for more information?=

amin.z · July 14, 2016, 01:30

You have some interface boundary conditions in your model, or at least fluent has detected some of the ( sometimes fluent detects them in a wrong way) you have to solve this problem before running the solver. assign your interface zones or change their type.

you could write the commands it TUI. for instance:
1. type mesh
2. enter
3. type check-verbosity ( or its abbreviation: cv)
4. enter
and...

Diger · July 14, 2016, 04:00

Hey again,
What in specific does interface in this case mean?
Interface to what?
And when I type this mesh/check-verbosity he then asks me for 4 different cases in each I do not get anything in return!?!?
edit: Ok I found out that the contact regions which arise due to the fact that I defined surface regions within inventor (via patch) on my fluid domain (which I wanted to use as inlets) but these contact regions / interfaces seem to make the problem, though I dont know why :-(

amin.z · July 14, 2016, 08:51

Interface boundary condition could be taken advantage when we need to connect two different zones especially in rotor- stator problems.
There is enough explanation about it in fluent documents.

about the TUI it depends on what you want to do. there is nothing to do with TUI in your case, you just have to check the boundary condition and use the suitable ones

July 13, 2016, 10:56	Fluent MESH check	#1
Diger Senior Member Join Date: Nov 2015 Posts: 135 Rep Power: 10	What does it mean when I check the quality of the mesh within fluent and it tells me: Checking mesh........................ WARNING: Unassigned interface zone detected for interface 10............ Done. WARNING: Mesh check failed. To get more detailed information about the mesh check failure increase the mesh check verbosity via the TUI command /mesh/check-verbosity.

July 14, 2016, 04:00		#4
Diger Senior Member Join Date: Nov 2015 Posts: 135 Rep Power: 10	Hey again, What in specific does interface in this case mean? Interface to what? And when I type this mesh/check-verbosity he then asks me for 4 different cases in each I do not get anything in return!?!? edit: Ok I found out that the contact regions which arise due to the fact that I defined surface regions within inventor (via patch) on my fluid domain (which I wanted to use as inlets) but these contact regions / interfaces seem to make the problem, though I dont know why :-( Last edited by Diger; July 14, 2016 at 05:33.

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
how to set periodic boundary conditions	Ganesh	FLUENT	15	November 18, 2020 06:09
[Other] Pointwise Mesh into Fluent - Error: "Divergence detected in AMG solver: ads-0."	kyles.sverige	ANSYS Meshing & Geometry	3	January 27, 2015 12:28
[ICEM] Missing face error from FLUENT even after repairing mesh + other questions	unknown159	ANSYS Meshing & Geometry	0	July 5, 2013 20:18
Transport mesh from ICEM CFD, to Fluent, to Sysnoise	Wieland	FLUENT	2	April 15, 2012 06:28
Fluent mesh Check error	Mohsin	FLUENT	6	August 31, 2011 04:03

July 13, 2016, 15:42		#2
Diger Senior Member Join Date: Nov 2015 Posts: 135 Rep Power: 10	And where exactly am I supposed to type this TUI command /mesh/check-verbosity for more information?=

July 14, 2016, 01:30		#3
amin.z Senior Member Amin Join Date: Oct 2013 Location: Germany Posts: 397 Rep Power: 14	You have some interface boundary conditions in your model, or at least fluent has detected some of the ( sometimes fluent detects them in a wrong way) you have to solve this problem before running the solver. assign your interface zones or change their type. you could write the commands it TUI. for instance: 1. type mesh 2. enter 3. type check-verbosity ( or its abbreviation: cv) 4. enter and...

July 14, 2016, 08:51		#5
amin.z Senior Member Amin Join Date: Oct 2013 Location: Germany Posts: 397 Rep Power: 14	Interface boundary condition could be taken advantage when we need to connect two different zones especially in rotor- stator problems. There is enough explanation about it in fluent documents. about the TUI it depends on what you want to do. there is nothing to do with TUI in your case, you just have to check the boundary condition and use the suitable ones