CFD Online Discussion Forums - [snappyHexMesh] Snappyhexmesh parallel run

Guys,

I was meshing a bluff body using sHM. I was able to do it serially but when i tried to do it in parallel, i got the following error stating "2D mesh-motion probably not correct in parallel". If anyone can figure out the reason for this please help me out guys. I attached my sHM dict file and the log file.

Code:

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] 

[0] #0  Foam::error::printStack(Foam::Ostream&) at ??:?

[0] #1  Foam::error::abort() at ??:?

[0] #2  Foam::twoDPointCorrector::calcAddressing() const at ??:?

[0] #3  Foam::twoDPointCorrector::normalEdgeIndices() const at ??:?

[0] #4  Foam::motionSmootherAlgo::modifyMotionPoints(Foam::Field<Foam::Vector<double> >&) const at ??:?

[0] #5  Foam::motionSmootherAlgo::curPoints() const at ??:?

[0] #6  Foam::motionSmootherAlgo::scaleMesh(Foam::List<long>&, Foam::List<Foam::Pair<long> > const&, Foam::dictionary const&, Foam::dictionary const&, bool, long) at ??:?

[0] #7  Foam::motionSmootherAlgo::scaleMesh(Foam::List<long>&, Foam::List<Foam::Pair<long> > const&, bool, long) at ??:?

[0] #8  Foam::autoSnapDriver::preSmoothPatch(Foam::meshRefinement const&, Foam::snapParameters const&, long, Foam::List<Foam::Pair<long> > const&, Foam::motionSmoother&) at ??:?

[0] #9  Foam::autoSnapDriver::doSnap(Foam::dictionary const&, Foam::dictionary const&, double, double, Foam::snapParameters const&) at ??:?

[0] #10  ? at ??:?

[0] #11  __libc_start_main in "/lib/x86_64-linux-gnu/libc.so.6"

[0] #12  ? at ??:?

--------------------------------------------------------------------------

MPI_ABORT was invoked on rank 0 in communicator MPI_COMM_WORLD 

with errorcode 1.



NOTE: invoking MPI_ABORT causes Open MPI to kill all MPI processes.

You may or may not see output from other processes, depending on

exactly when Open MPI kills them.

--------------------------------------------------------------------------

--------------------------------------------------------------------------

mpirun has exited due to process rank 0 with PID 7659 on

node vignesh-Lenovo-S510Pad-S510P-Touch exiting improperly. There are two reasons this could occur:



1. this process did not call "init" before exiting, but others in

the job did. This can cause a job to hang indefinitely while it waits

for all processes to call "init". By rule, if one process calls "init",

then ALL processes must call "init" prior to termination.



2. this process called "init", but exited without calling "finalize".

By rule, all processes that call "init" MUST call "finalize" prior to

exiting or it will be considered an "abnormal termination"



This may have caused other processes in the application to be

terminated by signals sent by mpirun (as reported here).

--------------------------------------------------------------------------

I tried hierarchical and scotch thinking it was a problem with decomposition. But both of them gave me the same error. Please help me out guys.:)

Thank you

Vicky