안녕하십니까 snappyHexMesh 를 parallel로 구동하는 과정에서 문제점이 발생하여 문의 드립니다. 제가 지금 airfoil을 sHM를 이용하여 격자생성을 수행하고 있는데요 serial로 sHM를 이용하면 잘 well working하는데 parallel을 하게되면 snap과정에서 아래와 같은 에러가 발생합니다. decomposePar 에서 hierarchical mothod로 6개로 도메인을 나누었습니다.
어떠한 문제이며 해결책이 있으면 코멘트 부탁 드립니다.
=================================================================== Scaling iteration 0 Moving mesh using diplacement scaling : min:1 max:1 Correcting 2-D mesh motion--> FOAM Warning : From function motionSmoother::movePoints(pointField& newPoints) in file motionSmoother/motionSmoother.C at line 873 2D mesh-motion probably not correct in parallel --> FOAM Warning : From function twoDPointCorrector::twoDPointCorrector(const polyMesh& mesh, const vector& n) in file twoDPointCorrector/twoDPointCorrector.C at line 152 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::twoDPointCorrector(const polyMesh& mesh, const vector& n) in file twoDPointCorrector/twoDPointCorrector.C at line 164 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: 33471 number of points: 34687 ...done [4] processorPolyPatch::calcGeometry : Writing my 925 faces to OBJ file "/home/sunghwan/test/iced_test/EG1162/processor4/procBoundary4to5_faces.obj" [5] processorPolyPatch::calcGeometry : Writing my 925 faces to OBJ file "/home/sunghwan/test/iced_test/EG1162/processor5/procBoundary5to4_faces.obj" [2] processorPolyPatch::calcGeometry : Writing my 1711 faces to OBJ file "/home/sunghwan/test/iced_test/EG1162/processor2/procBoundary2to5_faces.obj" [5] processorPolyPatch::calcGeometry : Dumping cell centre lines between corresponding face centres to OBJ file"/home/sunghwan/test/iced_test/EG1162/processor5/procBoundary5to4_faceCentresConnections.obj" [4] processorPolyPatch::calcGeometry : Dumping cell centre lines between corresponding face centres to OBJ file"/home/sunghwan/test/iced_test/EG1162/processor4/procBoundary4to5_faceCentresConnections.obj" [5] [5] [5] --> FOAM FATAL ERROR: [5] face 254 area does not match neighbour by 0.27707% -- possible face ordering problem. patch:procBoundary5to4 my area:1.46535e-05 neighbour area:1.46941e-05 matching tolerance:7.39708e-10 Mesh face:86705 vertices:4((0.925781 -0.0507812 0.015625) (0.925781 -0.0507812 0.0118529) (0.921875 -0.0507812 0.0118945) (0.921875 -0.0507812 0.015625)) If you are certain your matching is correct you can increase the 'matchTolerance' setting in the patch dictionary in the boundary file. Rerun with processor debug flag set for more information. [5] [5] From function processorPolyPatch::calcGeometry() [5] in file meshes/polyMesh/polyPatches/constraint/processor/processorPolyPatch.C at line 242. [5] FOAM parallel run exiting [5] -------------------------------------------------------------------------- MPI_ABORT was invoked on rank 5 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. -------------------------------------------------------------------------- [2] processorPolyPatch::calcGeometry : Dumping cell centre lines between corresponding face centres to OBJ file"/home/sunghwan/test/iced_test/EG1162/processor2/procBoundary2to5_faceCentresConnections.obj" [4] [4] [4] --> FOAM FATAL ERROR: [4] face 254 area does not match neighbour by 0.27707% -- possible face ordering problem. patch:procBoundary4to5 my area:1.46941e-05 neighbour area:1.46535e-05 matching tolerance:7.38449e-10 Mesh face:87991 vertices:4((0.925781 -0.0507812 0.015625) (0.921875 -0.0507812 0.015625) (0.921875 -0.0507812 0.0118737) (0.925781 -0.0507812 0.0118529)) If you are certain your matching is correct you can increase the 'matchTolerance' setting in the patch dictionary in the boundary file. Rerun with processor debug flag set for more information. [4] [4] From function processorPolyPatch::calcGeometry() [4] in file meshes/polyMesh/polyPatches/constraint/processor/processorPolyPatch.C at line 242. [4] FOAM parallel run exiting [4] -------------------------------------------------------------------------- mpirun has exited due to process rank 5 with PID 8002 on node sunghwan-System-Product-Name 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). |