|
[Sponsors] |
Error: Face processing failed 2D(Pointwise to Fluent) |
|
LinkBack | Thread Tools | Search this Thread | Display Modes |
May 18, 2018, 13:32 |
Error: Face processing failed 2D(Pointwise to Fluent)
|
#1 |
New Member
Aaron
Join Date: Jan 2018
Posts: 7
Rep Power: 8 |
I am working on a 2-D axisymmetric simulation where I have meshed using interior partition lines to make every domain structured. During the boundary condition phase, I continue to have the same error message regarding only a few of the boundaries.
Error: Face processing failed *Inconsistent domain normal *Incompatible BC types used on opposite sides of a baffle or connection *Non-manifold connectivity I have checked the domain normal(All positive K) as well as the non-manifold connectivity(I think) which leaves the BC types used on opposite sides as the problem. It is only a few random boundaries that cause this issue after some painful debugging(less than 10 out of the 150 boundaries). Some times when I leave them set as unspecified it imports, sometimes it doesn't. After struggling for over a month trying to search and figure out the issue, I need some help. If anyone has and incite to try and help fix the issue, it would be greatly appreciated. Again, this is a 2-d axisymmetric problem with boundary conditions causing the error when exporting to CAE. I have attached the overview of the drawing as well as an example of two boundaries that are causing the issue. |
|
May 19, 2018, 16:34 |
|
#2 |
Senior Member
John Chawner
Join Date: Mar 2009
Location: Fort Worth, Texas, USA
Posts: 275
Rep Power: 18 |
Aaron, because you say you've struggled for over a month I suggest you email our Technical Support at support@pointwise.com. Provide your Customer ID and description of your problem.
__________________
John Chawner / jrc@pointwise.com / www.pointwise.com Blog: http://blog.pointwise.com/ on Twitter: @jchawner |
|
May 19, 2018, 17:07 |
|
#3 | |
New Member
Aaron
Join Date: Jan 2018
Posts: 7
Rep Power: 8 |
Quote:
I feel like it’s something simple I’m overlooking since it’s only 2D and only a few BCs that cause the export error, but I’m still struggling with it. I appreciate the thought. |
||
May 19, 2018, 17:26 |
|
#4 |
Senior Member
John Chawner
Join Date: Mar 2009
Location: Fort Worth, Texas, USA
Posts: 275
Rep Power: 18 |
That's unfortunate. I don't know what version of the software you're using but it may be old enough that there have been changes to the Fluent export.
I have a vague recollection that Fluent didn't like axisymmetric geometry that had a true singularity along the axis of rotation (i.e. it required a small "tube" down the center). Is that still the case? I'm not a Fluent user but "non-manifold connectivity" means it can't figure out how to reassemble the mesh into a consistent whole. Have you set this up for 2D Fluent or 3D?
__________________
John Chawner / jrc@pointwise.com / www.pointwise.com Blog: http://blog.pointwise.com/ on Twitter: @jchawner |
|
May 19, 2018, 18:09 |
|
#5 | |
New Member
Aaron
Join Date: Jan 2018
Posts: 7
Rep Power: 8 |
Quote:
As far as fluent, to my knowledge it just requires the x axis as the line of rotation. I did get one export to not fail, but only if I left all BC as unspecified. It auto sets as wall in fluent, but They can be changed after. The only down side is you can’t set interior conditions once in fluent, so all my partition lines will have wall conditions instead of through/interior. Not 100 percent on how that will skew the results given both sides of the partition use the same material in fluent. In fluent, I can set the thickness to zero, but there might have some influence from contact resistance. This week I’m going to build a cas from the file that did export with all unspecified and see how fluent handles that. |
||
May 19, 2018, 18:31 |
|
#6 |
Senior Member
John Chawner
Join Date: Mar 2009
Location: Fort Worth, Texas, USA
Posts: 275
Rep Power: 18 |
Wait. The messages you quoted are from Pointwise during export? Or from Fluent during Import?
__________________
John Chawner / jrc@pointwise.com / www.pointwise.com Blog: http://blog.pointwise.com/ on Twitter: @jchawner |
|
May 19, 2018, 19:46 |
|
#7 |
Senior Member
David Garlisch
Join Date: Jan 2013
Location: Fidelity Pointwise, Cadence Design Systems (Fort Worth, Texas Office)
Posts: 307
Rep Power: 14 |
Please attach a zip of the pw file.
List the names of the connectors giving you the problem. In general, if all normals are consistent, the remaining issue will be incompatible BC types on opposite sides of internal, inter-domain cons. You cannot have a permeable BC type on one side, and a non-permeable type on the other. Permeable types are fan, radiator, porous IIRC. Another test to run is to remove all BCs and see if export succeeds. |
|
May 20, 2018, 10:38 |
|
#8 |
New Member
Aaron
Join Date: Jan 2018
Posts: 7
Rep Power: 8 |
||
May 20, 2018, 10:46 |
|
#9 | |
New Member
Aaron
Join Date: Jan 2018
Posts: 7
Rep Power: 8 |
Quote:
If I remove the BC and switch to unspecified on one of my grids, it created the CAE. I’m only trying to use interior,wall,interface conditions. Nothing fancy. It’s a transient heat transfer problem with natural convection. During the debug stage I recreated the drawing multiple times by drawing it directly in pointwise making sure to have connections and grid points on the ends of connectors. Then moving from one section at a time assign the BCs. Out of the 150BCs the connectors only 6-10 BCs (3-5 connectors) cause the error. I will upload first thing Monday, and I appreciate the knowledge. |
||
May 21, 2018, 11:46 |
|
#10 | |
New Member
Aaron
Join Date: Jan 2018
Posts: 7
Rep Power: 8 |
Quote:
https://www.dropbox.com/sh/uii6ewdlt...BzdgEjpna?dl=0 I have set the BCs which are interior already and cause no issues The BCs that are set as unspecified can be changed inside of fluent, so those are not an issue either. The 6 connector BCs are the issue at this point Con-1 same/opposite (Vial tip/vial air gap) Con-17 same/opposite (Vial body base/vial air gap) Con-99 same/opposite (Vial gap right/base upper pdms) I appreciate you taking a look at this for me. I feel as it is an easy fix, but I'm stuck. |
||
May 21, 2018, 13:59 |
|
#11 | |
Senior Member
David Garlisch
Join Date: Jan 2013
Location: Fidelity Pointwise, Cadence Design Systems (Fort Worth, Texas Office)
Posts: 307
Rep Power: 14 |
I downloaded your file.
I loaded it into the current release of Pointwise V18.1 (2018-03-20 20:27:00) Windows 64-bit Without changing anything, the file as you downloaded exported without error. Then, I set the BCs to the three connection cons you listed:
This also exported without error. I noticed the pw file header indicated you are using Pointwise V18.0R3 Mon May 21 14:07:17 (GMT) 2018 I was able to repeat the error! Quote:
You will need to update your version. |
||
May 22, 2018, 11:01 |
|
#12 | |
New Member
Aaron
Join Date: Jan 2018
Posts: 7
Rep Power: 8 |
Quote:
The exact version installed currently is...Pointwise V18.0 Release 3 -- Optimized Build 0209161753 (2017-05-16 17:53:00) Windows 64-bit Again, I appreciate the prompt replay and knowledge. |
||
January 5, 2023, 14:19 |
|
#13 | |
New Member
karnataka
Join Date: May 2017
Posts: 4
Rep Power: 9 |
Quote:
I had mixed grids on my baffle surface and when the volume mesher was done , it would locally modify the grids on the baffle surface. When I brought in the .vml file that pointwise suggests , it showed me which cells were problematic . From the comments in this and other posts I figured that the problem might be related to mixed grids near that part of the geo. So I locally meshed the baffle in the problematic area only with tri cells and it worked. Hopefully this helps someone struggling with the same issue |
||
Tags |
fluent, pointwise |
|
|
Similar Threads | ||||
Thread | Thread Starter | Forum | Replies | Last Post |
Problem in using parallel process in fluent 14 | Tleja | FLUENT | 3 | September 13, 2013 11:54 |
Parallel Processing Problems Fluent 13 | lstebe | FLUENT | 3 | February 15, 2012 10:54 |
DeardorffDiffStress turbulence model | Zuixy | OpenFOAM Running, Solving & CFD | 0 | November 14, 2011 09:44 |
[OpenFOAM] ParaView/Parafoam error when making animation | Disco_Caine | ParaView | 6 | September 28, 2010 10:54 |
Fluent Parallel Processing | Mrxlazuardin | FLUENT | 2 | April 28, 2010 08:36 |