CFD Online URL
[Sponsors]
Home > Forums > CFX

Why Non-overlap interface occur in 1 to 1 mesh?

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

Reply
 
LinkBack Thread Tools Display Modes
Old   November 19, 2006, 01:39
Default Why Non-overlap interface occur in 1 to 1 mesh?
  #1
kake
Guest
 
Posts: n/a
As you know, in cfx, we only can specify GGI interface type to a 1 to 1 mesh when modelling rotor stator question. But one question comes out, the non overlap area fraction will occur in the physically matching 1 to 1 interface.That is to say, the non overlap will be regarded as wall defaultly. So this is very surperising. Any one know how CFX determine this ? According what? Which range we can accept? Can we cancle this determination instead of specifying 1 to 1 physically?
  Reply With Quote

Old   November 20, 2006, 12:51
Default Re: Why Non-overlap interface occur in 1 to 1 mesh
  #2
Robin
Guest
 
Posts: n/a
GGI is always used to handle frame changes, regarless of whether the mesh is 1:1 or not. This is nothing to be concerned with. The non-overlap conditions in the boundary condition specification is only used if there are non-overlap regions. If the mesh is truly 1:1, there will be no non-overlap regions.

Read the doc for details.

Regards, Robin
  Reply With Quote

Old   November 22, 2006, 23:24
Default Re: Why Non-overlap interface occur in 1 to 1 mesh
  #3
kake
Guest
 
Posts: n/a
Thanks,Robin

In fact,my mesh is truly 1:1,because the mesh is made in icemcfd with a whole block.So this can guartee the mesh node matched.But unfortunally,CFX still report the non-overlap interface region,and which occur a large fraction of the interface. So i am very surprising. My question is: According which criteria does cfx determine this? Which range can we accept?

when i check my results, the nov overlap region has been regarded as the wall.
  Reply With Quote

Old   November 23, 2006, 11:26
Default Re: Why Non-overlap interface occur in 1 to 1 mesh
  #4
Robin
Guest
 
Posts: n/a
Hi Kake,

Is the solver reporting non-overlap?

If it is a Frozen Rotor interface, the interface must be a surface of revolution about your axis of rotation. If it is not, it is possible to get this error. Check that it is and fix it as necessary, then run again.

Regards, Robin
  Reply With Quote

Old   November 24, 2006, 05:58
Default Re: Why Non-overlap interface occur in 1 to 1 mesh
  #5
kake
Guest
 
Posts: n/a
My interface type is Stage. I think it is not related to the interface type. So i'd like to know how cfx determine non overlap between two interfaces? If you want to prove my question? you also can check the tutorial case? which have the same question when you run it. it will appear in the solver *out file at the very begining.
  Reply With Quote

Old   November 24, 2006, 10:12
Default Re: Why Non-overlap interface occur in 1 to 1 mesh
  #6
Robin
Guest
 
Posts: n/a
Kake,

It can still be related to your interface type. If it is 1:1 and the edges of the regions match up, a regular GGI will report 0% overlap. That may not be the case with Stage or Frozen Rotor, so I'll ask you again, is your interface a surface of revolution? Are you domain's periodic?

Regards, Robin
  Reply With Quote

Old   November 26, 2006, 22:03
Default Re: Why Non-overlap interface occur in 1 to 1 mesh
  #7
kake
Guest
 
Posts: n/a
Thanks Robin,

in fact,i agree with your opinion.in my mesh, there are two interfaces of revolution surfaces, and the simulation domain is periodic.For the requriment of yplus,the mesh near the wall is very samll,which maybe smaller than the the geometric tollerance. So i suppose this maybe the reason.

Is it possible to override this determination of non overlap interface area in some expert mode?
  Reply With Quote

Old   November 27, 2006, 10:46
Default Re: Why Non-overlap interface occur in 1 to 1 mesh
  #8
Robin
Guest
 
Posts: n/a
If it is a frozen rotor or stage interface, you can manually specify the pitch ratio or pitch angles. Due to the finite nature of the mesh, it is sometimes possible to get some non-overlap due to discrete errors.

-Robin
  Reply With Quote

Old   December 14, 2006, 01:24
Default Re: Why Non-overlap interface occur in 1 to 1 mesh
  #9
HekLeR
Guest
 
Posts: n/a
Are you 100% absolutely certain, without any doubt, that the hub curve (lowest axial or radial position) of your interface mesh forms a perfect circle of revolution around the axis.

Are you 100% absolutely certain, without any doubt, that the hub & shroud curves on both sides of your interface mesh exactly line up, both forming the same circles of revolution around the axis.

If not, then you can get non-zero non-overlap area because the solver may not correctly figure out the pitch angles.

In this case, just set the pitch angles.
  Reply With Quote

Reply

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
[ICEM] Generating Mesh for STL Car in Windtunnel Simulation tommymoose ANSYS Meshing & Geometry 48 April 15, 2013 05:24
snappyHexMesh won't work - zeros everywhere! sc298 OpenFOAM Native Meshers: snappyHexMesh and Others 2 March 27, 2011 22:11
Spontaneous failure of moving mesh interface gareth__it_power ANSYS 1 August 26, 2010 08:50
Dynamic Mesh moving interface help akash.iitb FLUENT 0 August 24, 2010 00:53
fluent add additional zones for the mesh file SSL FLUENT 2 January 26, 2008 12:55


All times are GMT -4. The time now is 23:02.