Fluent Mesh Issue
Altair EmployeeHello,
I created a quad mesh for CFD application using HM 2017.2. I exported the same to Fluent. As far as I can tell, I went through the tutorials supplied by Altair about CFD meshing and other help posts here about exporting to Fluent.
My mesh is on a 2D surface and I extracted 1D elements using 'Edge' option and assigned them in to appropriate collectors.
When I import in to Fluent, I am not able to rotate or manipulate the mesh views to get my airfoil to display. All the controls for the same are greyed out. I don't face similar issues if I generate mesh using ANSYS application. It is possible that help for this may be beyond the scope of this forum and I may have to contact ANSYS/Fluent folks but I thought of checking in once here.
Attaching a few pictures at the end to illustrate my issue.
Here is what Fluent displays during reading the mesh information.
Buffering for file scan...
16497 nodes.
16232 mixed cells, zone 1.
59 mixed wall faces, zone 3.
471 mixed wall faces, zone 4.
32199 mixed interior faces, zone 5.
Building...
mesh
Info: The mesh contains elements that are invalid or of poor quality.
A different numerical scheme will be applied to these elements,
which may affect the quality of the solution. It is recommended
that you consider removing the invalid and poor quality elements
in the mesh.
For more information on the invalid and poor quality elements,
please use the following TUI commands:
/mesh/check
/mesh/repair-improve/report-poor-elements.
WARNING: 16232 cells with non-positive volume detected.
materials,
interface,
domains,
zones,
interior-5
far_field
airfoil
fluid
parallel,
Done.
Preparing mesh for display...
Done.
Writing Settings file '<xxx>\2D_Airfoil_HM_Export.set'...
writing rp variables ... Done.
writing domain variables ... Done.
writing fluid (type fluid) (mixture) ... Done.
writing airfoil (type wall) (mixture) ... Done.
writing far_field (type wall) (mixture) ... Done.
writing interior-5 (type interior) (mixture) ... Done.
writing zones map name-id ... Done.
Domain Extents:
x-coordinate: min (m) = 0.000000e+00, max (m) = 0.000000e+00
y-coordinate: min (m) = -2.599966e+02, max (m) = 6.400000e+02
Volume statistics:
WARNING: 16232 cells with non-positive volume detected.
minimum volume (m3): 0.000000e+00
maximum volume (m3): 0.000000e+00
total volume (m3): 0.000000e+00
Face area statistics:
minimum face area (m2): 0.000000e+00
maximum face area (m2): 1.196754e+01
Checking mesh..........
WARNING: left-handed faces detected on zone 3: 0 right-handed, 59 left-handed.
WARNING: left-handed faces detected on zone 4: 0 right-handed, 471 left-handed.
WARNING: left-handed faces detected on zone 5: 0 right-handed, 32199 left-handed..
WARNING: 64928 face(s) on cell zone 1 with wrong node order (on 0)................
Done.
WARNING: Mesh check failed.
Folks, who are familiar with HM to Fluent, would it be possible to diagnoze the possible issue?
Thanks,
- U
<?xml version="1.0" encoding="UTF-8"?>
<?xml version="1.0" encoding="UTF-8"?>
<?xml version="1.0" encoding="UTF-8"?>
Answers
-
It looks like that Fluent looks for volume elements while as you have only 2D elements.
0 -
Hi,
Fluent automatically considered the mesh as a 2D type during start up. Not sure why it would be looking for volume elements. In any case, I could not find a way to re-specify 2D analysis type in Fluent...so the issue still persists.
0 -
Just want to add a little bit more info if that's useful.
I received this warning in HM after exporting the solver deck. BTW component ID 1 is 'Fluid' collector compromising of 2D elements.
<?xml version="1.0" encoding="UTF-8"?>
Is it possible that Fluent is displaying only line elements due to issue with element normal direction during translation from HM to Fluent?
I did check of Normals in HM and they are aligned to -ve X axis and not +ve Z direction as mentioned the above warning.
Hope I can get some help...
Thanks.
0
