[johny]

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

[wadekar]

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

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

[DrFloyd]

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

[wadekar]

Originally Posted by DrFloyd

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

[DrFloyd]

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.

[ameya2310]

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