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

SnappyHexMesh Point is not inside Mesh but it is

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

Like Tree6Likes
  • 1 Post By andersking
  • 4 Post By madad2005
  • 1 Post By ziad

Reply
 
LinkBack Thread Tools Display Modes
Old   February 18, 2009, 10:19
Default Hi everyOne, maybe this is
  #1
Senior Member
 
Wolfgang Heydlauff
Join Date: Mar 2009
Location: Germany
Posts: 136
Rep Power: 8
wolle1982 is on a distinguished road
Hi everyOne,

maybe this is an easy one. Meshing with snappyHexMesh I sometimes get the error message:

Point (51 35 45) is not inside the mesh or on a face or edge.
Bounding box of the mesh-1500 -300 -500) (500 1200 1200)

From function refinementParameters::findCells(const polyMesh&) const
in file autoHexMesh/autoHexMeshDriver/refinementParameters/refinementParameters.C at line 104.

FOAM exiting


it tells me, that the point, that defines the keeping mesh zone, is not inside the initial mesh....but it is. i can try with a whole bunch of other coordinates with the same result (i don't think they all accidentely match a cell-face).

maybe someone of you had the same problem sometime and knows the answer. the case itself is a very simple one. i've already managed to mesh with sHM but this one is bugging me, because there seems no plausible explaination.
wolle1982 is offline   Reply With Quote

Old   August 4, 2009, 05:56
Default
  #2
New Member
 
Join Date: Aug 2009
Posts: 1
Rep Power: 0
beefcake883 is on a distinguished road
hi,

did you find out why this happens? I have the same problem.
beefcake883 is offline   Reply With Quote

Old   August 4, 2009, 22:24
Default
  #3
Member
 
Andrew King
Join Date: Mar 2009
Location: Perth, Western Australia, Australia
Posts: 81
Rep Power: 8
andersking is on a distinguished road
They key is in "... or on a face or edge", snappyHexMesh can't have the deciding point lie on a face or edge. Try something like (51.3141592654 35.3141592654 45.3141592654), instead of (51 35 45) - ie. something that is unlikely to come up during the cell divisions.

Cheers
Andrew
FrankFlow likes this.
__________________
Dr Andrew King
Fluid Dynamics Research Group
Curtin University
andersking is offline   Reply With Quote

Old   September 4, 2009, 09:18
Default
  #4
Senior Member
 
Anonymous
Join Date: Mar 2009
Posts: 110
Rep Power: 8
madad2005 is on a distinguished road
I'm also having this problem and increasing the number of deciaml places is not helping. Has anyone found a proper workaround for this?
madad2005 is offline   Reply With Quote

Old   September 4, 2009, 09:27
Default
  #5
Senior Member
 
Anonymous
Join Date: Mar 2009
Posts: 110
Rep Power: 8
madad2005 is on a distinguished road
...and I've just found the problem! Make sure you have defined your bounding box properly, starting with the face at minX then the face at maxX. Don't know if this is properly explaining what the issue was, but this works for me. See below:

vertices
(
( 750 -750 750)
( 750 750 750)
( 750 750 -750)
( 750 -750 -750)
(-750 -750 750)
(-750 750 750)
(-750 750 -750)
(-750 -750 -750)
);
blocks
(
//hex(0 3 2 1 4 7 6 5) (20 20 20) simpleGrading (1 1 1) <--this is wrong
hex (4 7 6 5 0 3 2 1) (20 20 20) simpleGrading (1 1 1) // this is correct
);
nisha, jiec827, ehsoon and 1 others like this.
madad2005 is offline   Reply With Quote

Old   December 16, 2009, 15:33
Default
  #6
Member
 
James Baker
Join Date: Dec 2009
Posts: 35
Rep Power: 7
fijinx is on a distinguished road
Worked perfect, thanks!
fijinx is offline   Reply With Quote

Old   September 3, 2010, 08:59
Default
  #7
Senior Member
 
Ziad Boutanios
Join Date: Mar 2009
Location: Montréal, Canada
Posts: 113
Rep Power: 8
ziad is on a distinguished road
The proper way to do it is to set up your blockMesh domain as per section 5.3 in the user guide. You should use the setup in figure 5.5 on page U-142.

right-handed coordinate system x1x2x3
x1 direction described by moving from vertex 0 to vertex 1
x2 direction described by moving from vertex 1 to vertex 2
vertices 0, 1, 2, 3 define the plane x3 = 0
vertex 4 is found by moving by moving from vertex 0 in the x3 direction
vertices 5,6 and 7 are similarly found by moving in the x3 direction from vertices 1,2
and 3 respectively
nisha likes this.
ziad is offline   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
Inside and outside mesh with snappyhexmesh nzy102 OpenFOAM Native Meshers: snappyHexMesh and Others 17 May 8, 2013 17:04
SnappyHexMesh meshes inside and outside of an STL geometry villier OpenFOAM Mesh Utilities 17 June 15, 2010 19:51
Point inside Cell bobatpurdue OpenFOAM Meshing & Mesh Conversion 7 November 11, 2008 21:32
Inside and outside mesh with snappyhexmesh nzy102 OpenFOAM Mesh Utilities 0 August 31, 2008 23:50
Inside and outside mesh with snappyhexmesh nzy102 OpenFOAM Mesh Utilities 0 August 31, 2008 23:44


All times are GMT -4. The time now is 07:29.