CFD Online Logo CFD Online URL
www.cfd-online.com
[Sponsors]
Home > Forums > Software User Forums > OpenFOAM > OpenFOAM Meshing & Mesh Conversion

[snappyHexMesh] Snappy fails to create layers

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

Like Tree9Likes
  • 7 Post By DrFloyd
  • 2 Post By ameya2310

Reply
 
LinkBack Thread Tools Search this Thread Display Modes
Old   May 29, 2015, 15:15
Default Snappy fails to create layers
  #1
New Member
 
johny
Join Date: Jul 2010
Posts: 28
Rep Power: 13
johny is on a distinguished road
Hello Foamers,
I've seemingly a simply problem but whatever I try I fail to solve it. I fail a create prism layers however simple the geometry is. To start with I've a a plane surface with a small hump and I want to create prsims on this surface. I'm generating a perfect volume mesh without the layers(at the boundary I just have steps). the following the error message. It would be great if anyone could provide some insight.
Cheers,



Smoothing patch points ...
Smoothing iteration 0
Found 0 non-mainfold point(s).

Scaling iteration 0
Moving mesh using displacement scaling : min:1 max:1
[2]
[2]
[2] --> FOAM FATAL ERROR:
[2] Cannot determine normal vector from patches.
[2]
[2] From function twoDPointCorrector::twoDPointCorrector(const polyMesh& mesh, const vector& n)
[2] in file twoDPointCorrector/twoDPointCorrector.C at line 103.
[2]
FOAM parallel run aborting
[2]
[3]
[3]
[3] --> FOAM FATAL ERROR:
[3] Cannot determine normal vector from patches.
[3]
[3] From function twoDPointCorrector::twoDPointCorrector(const polyMesh& mesh, const vector& n)
[3] in file twoDPointCorrector/twoDPointCorrector.C at line 103.
[3]
FOAM parallel run aborting
johny is offline   Reply With Quote

Old   June 27, 2016, 08:15
Default snappyHexMesh 'normal vector from patches'
  #2
New Member
 
Sandip Wadekar
Join Date: Oct 2014
Posts: 17
Rep Power: 9
wadekar is on a distinguished road
Hi Foamers

I am also facing the similar problem when running the snappyHexMesh. Can someone point out where and how to define the normal vector for the patches ?

Thanks in advance
Quote:
Scaling iteration 0
Moving mesh using displacement scaling : min:1 max:1
Correcting 2-D mesh motion--> FOAM Warning :
From function motionSmootherAlgo::modifyMotionPoints(pointField& )
in file motionSmoother/motionSmootherAlgo.C at line 660
2D mesh-motion probably not correct in parallel
[0]
[0]
[0] --> FOAM FATAL ERROR:
[0] Cannot determine normal vector from patches.
[0]
[0] From function twoDPointCorrector::calcAddressing()
[0] in file twoDPointCorrector/twoDPointCorrector.C at line 105.
[0]
FOAM parallel run aborting
[0]
[1]
[1]
[1] --> FOAM FATAL ERROR:
[1] Cannot determine normal vector from patches.
[1]
[1] From function twoDPointCorrector::calcAddressing()
[1] in file twoDPointCorrector/twoDPointCorrector.C at line 105.
[1]
FOAM parallel run aborting
[1]
[2]
[2]
[2] --> FOAM FATAL ERROR:
[2] Cannot determine normal vector from patches.
[2]
[2] From function twoDPointCorrector::calcAddressing()
[2] in file twoDPointCorrector/twoDPointCorrector.C at line 105.
[2]
FOAM parallel run aborting
[2]
[3]
[3]
[3] --> FOAM FATAL ERROR:
[3] Cannot determine normal vector from patches.
[3]
[3] From function twoDPointCorrector::calcAddressing()
[3] in file twoDPointCorrector/twoDPointCorrector.C at line 105.
[3]
FOAM parallel run aborting
wadekar is offline   Reply With Quote

Old   February 5, 2017, 04:56
Default same problem
  #3
New Member
 
Join Date: Oct 2014
Posts: 24
Rep Power: 9
DrFloyd is on a distinguished road
Hi guys,
I have the same problem! Snappy doesn't work in parallel and it fails when starts "Morphing phase" with this error:


Smoothing patch points ...
Smoothing iteration 0
Found 0 non-manifold point(s).

Scaling iteration 0
Moving mesh using displacement scaling : min:1 max:1
Correcting 2-D mesh motion--> FOAM Warning :
From function motionSmootherAlgo::modifyMotionPoints(pointField& )
in file motionSmoother/motionSmootherAlgo.C at line 660
2D mesh-motion probably not correct in parallel
[1]
[1]
[1] --> FOAM FATAL ERROR:
[1] Cannot determine normal vector from patches.
[1]
[1] From function twoDPointCorrector::calcAddressing()
[1] in file twoDPointCorrector/twoDPointCorrector.C at line 105.
[1]
FOAM parallel run aborting
[1]
[1] #0 Foam::error:rintStack(Foam::Ostream&) at ??:?
[1] #1 Foam::error::abort() at ??:?
[1] #2 Foam::twoDPointCorrector::calcAddressing() const at ??:?
[1] #3 Foam::twoDPointCorrector::normalEdgeIndices() const at ??:?
[1] #4 Foam::motionSmootherAlgo::modifyMotionPoints(Foam: :Field<Foam::Vector<double> >&) const--> FOAM Warning :
From function twoDPointCorrector::calcAddressing()
in file twoDPointCorrector/twoDPointCorrector.C at line 151
the number of vertices in the geometry is odd - this should not be the case for a 2-D case. Please check the geometry.
--> FOAM Warning :
From function twoDPointCorrector::calcAddressing()
in file twoDPointCorrector/twoDPointCorrector.C at line 160
The number of points in the mesh is not equal to twice the number of edges normal to the plane - this may be OK only for wedge geometries.
Please check the geometry or adjust the orthogonality tolerance.

Number of normal edges: 809961 number of points: 821755.

Did you find a solution?

Thankyou in advance
DrFloyd is offline   Reply With Quote

Old   February 6, 2017, 04:09
Default
  #4
New Member
 
Sandip Wadekar
Join Date: Oct 2014
Posts: 17
Rep Power: 9
wadekar is on a distinguished road
Quote:
Originally Posted by DrFloyd View Post
Hi guys,
I have the same problem! Snappy doesn't work in parallel and it fails when starts "Morphing phase" with this error:


Smoothing patch points ...
Smoothing iteration 0
Found 0 non-manifold point(s).

Scaling iteration 0
Moving mesh using displacement scaling : min:1 max:1
Correcting 2-D mesh motion--> FOAM Warning :
From function motionSmootherAlgo::modifyMotionPoints(pointField& )
in file motionSmoother/motionSmootherAlgo.C at line 660
2D mesh-motion probably not correct in parallel
[1]
[1]
[1] --> FOAM FATAL ERROR:
[1] Cannot determine normal vector from patches.
[1]
[1] From function twoDPointCorrector::calcAddressing()
[1] in file twoDPointCorrector/twoDPointCorrector.C at line 105.
[1]
FOAM parallel run aborting
[1]
[1] #0 Foam::error:rintStack(Foam::Ostream&) at ??:?
[1] #1 Foam::error::abort() at ??:?
[1] #2 Foam::twoDPointCorrector::calcAddressing() const at ??:?
[1] #3 Foam::twoDPointCorrector::normalEdgeIndices() const at ??:?
[1] #4 Foam::motionSmootherAlgo::modifyMotionPoints(Foam: :Field<Foam::Vector<double> >&) const--> FOAM Warning :
From function twoDPointCorrector::calcAddressing()
in file twoDPointCorrector/twoDPointCorrector.C at line 151
the number of vertices in the geometry is odd - this should not be the case for a 2-D case. Please check the geometry.
--> FOAM Warning :
From function twoDPointCorrector::calcAddressing()
in file twoDPointCorrector/twoDPointCorrector.C at line 160
The number of points in the mesh is not equal to twice the number of edges normal to the plane - this may be OK only for wedge geometries.
Please check the geometry or adjust the orthogonality tolerance.

Number of normal edges: 809961 number of points: 821755.

Did you find a solution?

Thankyou in advance
I think its because of normal direction.
The point you have defined in the snappyHexMesh must be belong inside the domain.

Thanks
wadekar is offline   Reply With Quote

Old   February 6, 2017, 06:21
Default
  #5
New Member
 
Join Date: Oct 2014
Posts: 24
Rep Power: 9
DrFloyd is on a distinguished road
Dear wadekar,
thanks for your reply.

I have solved my problem. When you run SHM in parallel it's recommended not having "empty" type surfaces in file boundary of root case polymesh.

Best regards.
DrFloyd is offline   Reply With Quote

Old   November 6, 2020, 07:13
Thumbs up Cannot determine normal vector from patches. [4] [4] From function void Foam::tw
  #6
New Member
 
Ameya
Join Date: Jan 2018
Posts: 5
Rep Power: 6
ameya2310 is on a distinguished road
Hello Guys,
I struggled with the same issue.
And in my case, I wall creating base mesh which was slightly smaller than my geometry. Once I fixed it, the problem disappeared.

Thanks.
Ameya
obiscolly50 and kennyadapter like this.
ameya2310 is offline   Reply With Quote

Reply

Thread Tools Search this Thread
Search this Thread:

Advanced Search
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 Off
Pingbacks are On
Refbacks are On


Similar Threads
Thread Thread Starter Forum Replies Last Post
[snappyHexMesh] Trouble with snappy and boundary layers kellard OpenFOAM Meshing & Mesh Conversion 12 February 12, 2019 05:12
Error while running pisoFoam with snappy but ran smoothly without snappy in empty dm faiazk OpenFOAM Running, Solving & CFD 0 October 24, 2018 13:51
[GAMBIT] How to plot S pipe mariam.sara ANSYS Meshing & Geometry 36 November 7, 2013 15:22
Actuator disk model audrich FLUENT 0 September 21, 2009 07:06
Where's the singularity/mesh flaw? audrich FLUENT 3 August 4, 2009 01:07


All times are GMT -4. The time now is 08:17.