CFD Online Logo CFD Online URL
www.cfd-online.com
[Sponsors]
Home > Forums > CFX

Unable to import mesh - identify problematic face

Register Blogs Members List Search Today's Posts Mark Forums Read

Reply
 
LinkBack Thread Tools Display Modes
Old   April 17, 2014, 06:01
Default Unable to import mesh - identify problematic face
  #1
TWA
New Member
 
Join Date: Sep 2011
Location: Norway
Posts: 10
Rep Power: 5
TWA is on a distinguished road
Hi,

I'm importing a large mesh containing several bodies into CFX-Pre. The mesh is made in ANSYS Meshing (Workbench, ANSYS 15). Pre starts to load the mesh, but upon completing, i get the error message as seen in the attachment.

The mesh has (should have?) matching connections, i.e. the mesh is continuous throughout the bodies. But the error message indicate that there may be a face where this is not true and the mesh is bad. Problem is that since the mesh will not load in Pre, how do I identify this face (F434.x) given in the error message?

The mesh contains hundreds of faces, so I cant check them all manually. But I have checked the mesh at certain "high risk" locations without observing anything out of the ordinary.
Attached Images
File Type: png meshfail.PNG (18.6 KB, 21 views)
TWA is offline   Reply With Quote

Old   April 17, 2014, 08:47
Default
  #2
Senior Member
 
Matthias Voß
Join Date: Mar 2009
Location: Berlin, Germany
Posts: 446
Rep Power: 11
mvoss is on a distinguished road
Maybe you can disable the automatic interface creation for the mesh to load at least.
mvoss is offline   Reply With Quote

Old   April 17, 2014, 08:58
Default
  #3
TWA
New Member
 
Join Date: Sep 2011
Location: Norway
Posts: 10
Rep Power: 5
TWA is on a distinguished road
Yes, already tried that. The same error message appears :/ (Disabled both in the import mesh window and in the general case options)
TWA is offline   Reply With Quote

Old   April 17, 2014, 09:01
Default
  #4
Senior Member
 
Matthias Voß
Join Date: Mar 2009
Location: Berlin, Germany
Posts: 446
Rep Power: 11
mvoss is on a distinguished road
Did you try to find the vertex 202 instead of the the face 4**?
mvoss is offline   Reply With Quote

Old   April 19, 2014, 09:50
Default
  #5
TWA
New Member
 
Join Date: Sep 2011
Location: Norway
Posts: 10
Rep Power: 5
TWA is on a distinguished road
I don't really know how to find that either...

But at least I have some progress. By suppressing several bodies and using trial and error, I've identified the face in the error message. I've also discovered that there are a few more faces in the mesh which produce the same error Now I have to see if I am able to fix the first one...
TWA is offline   Reply With Quote

Old   April 29, 2014, 07:52
Default
  #6
TWA
New Member
 
Join Date: Sep 2011
Location: Norway
Posts: 10
Rep Power: 5
TWA is on a distinguished road
When I tried to construct the mesh in 14.5, it was successfully imported to CFX Pre 15, so I suspected this to be a bug. I got this confirmed by Ansys today:

Quote:
Yes, this is a reported bug. It is fixed till next release, R16. So, unfortunately you need to use the previous version 14.5.7.

I'm sorry for any inconvenience.

Regards
Tomas

Thank you,
ANSYS Technical Support
TWA is offline   Reply With Quote

Old   April 29, 2014, 09:03
Default
  #7
Senior Member
 
Edmund Singer P.E.
Join Date: Aug 2010
Location: Minneapolis, MN
Posts: 494
Rep Power: 11
singer1812 is on a distinguished road
Im not a big WB Mesher for CFD user, but this seems incredible!

Can you explain exactly what the bug was? Is Pre unable to import Multi-Body Meshes from WB? And no fix till 16 seems unreasonable for a problem you describe. Was there no other work around? Did you get past tier 1 support?
singer1812 is offline   Reply With Quote

Old   May 2, 2014, 02:49
Default
  #8
TWA
New Member
 
Join Date: Sep 2011
Location: Norway
Posts: 10
Rep Power: 5
TWA is on a distinguished road
Quote:
Originally Posted by singer1812 View Post
Im not a big WB Mesher for CFD user, but this seems incredible!

Can you explain exactly what the bug was? Is Pre unable to import Multi-Body Meshes from WB? And no fix till 16 seems unreasonable for a problem you describe. Was there no other work around? Did you get past tier 1 support?
The problem was that 1:1 mesh was not fulfilled on some mesh interfaces. The bug is probably in the mesh program. I don't know why the problem occurs on just a few interfaces... I was able to import multi-body mesh with 1:1 mesh when I suppressed several "problematic" bodies, so the problem is not general.

When constructing the mesh in Ansys 14.5 (with exactly the same geometry input and settings), it worked fine to import it in Pre 15.

What is tier 1 support?
TWA is offline   Reply With Quote

Old   May 2, 2014, 08:46
Default
  #9
Senior Member
 
Edmund Singer P.E.
Join Date: Aug 2010
Location: Minneapolis, MN
Posts: 494
Rep Power: 11
singer1812 is on a distinguished road
Tier 1 support is the guy you first talk to. Usually it is a general support engineer and not the developers. I have found that sometimes (for harder problems) the support engineers write off things as unworkable, or propose an ineligant solution, that a developer would correct.

Now that you have described the problem a bit more, I have seen the meshing issue that you describe (at 14.5 and prior). I have even seen the opposite where I want 2 distinct bodies with a 1:1 continuous mesh connect between them and the WB mesher will import the geometry as 1 body (even though it is 2 bodies in DM).

I have found that it usually means the body is badly built in DM. To fix it, I usually build up the offending body again from scratch, in a slightly different way, and the problem in the mesher goes away.
singer1812 is offline   Reply With Quote

Old   May 7, 2014, 02:51
Default
  #10
TWA
New Member
 
Join Date: Sep 2011
Location: Norway
Posts: 10
Rep Power: 5
TWA is on a distinguished road
Ok, I used the "Siebel eCustomer Portal 8.1" on the Ansys Customer Portal.

Yes, after a few years working with this software, I too have experienced problems such as you describe. I tried to re-model the problematic bodies, but it didn't help.

This is the first time I have experienced problems when importing a seemingly good mesh into Pre, and that's why I suspected it to be a bug rather than a dirty geometry. With dirty geometries, the problems always appear when importing the geometry into the meshing software, or during the meshing itself. At least that's my experience
TWA is offline   Reply With Quote

Reply

Tags
connection, interfaces, mesh

Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are On


Similar Threads
Thread Thread Starter Forum Replies Last Post
Moving mesh Niklas Wikstrom (Wikstrom) OpenFOAM Running, Solving & CFD 122 June 15, 2014 06:20
how to set periodic boundary conditions Ganesh FLUENT 13 January 22, 2014 05:11
(gambit)projecting just a part of mesh on another face? gholamghar ANSYS Meshing & Geometry 2 March 14, 2011 18:14
Trimmed cell and embedded refinement mesh conversion issues michele OpenFOAM Other Meshers: ICEM, Star, Ansys, Pointwise, GridPro, Ansa, ... 2 July 15, 2005 04:15
How to control Minximum mesh space? hung FLUENT 7 April 18, 2005 09:38


All times are GMT -4. The time now is 04:57.