|
[Sponsors] |
[snappyHexMesh] mpirun error on with addLayer ON |
|
LinkBack | Thread Tools | Search this Thread | Display Modes |
May 4, 2019, 13:35 |
mpirun error on with addLayer ON
|
#1 |
Member
Joe lee
Join Date: Nov 2018
Posts: 59
Rep Power: 8 |
I am runnning snappyHexMesh on my stl mode, and I am an error like this:
Code:
... ... patch faces layers avg thickness[m] near-wall overall ----- ----- ------ --------- ------- figure 9684 3 5.94 18.2 Selecting externalDisplacementMeshMover displacementMedialAxis displacementMedialAxis : Calculating distance to Medial Axis ... displacementMedialAxis : Smoothing normals ... Iteration 0 residual 0.101218 displacementMedialAxis : Inserting points on patch frontAndBack if angle to nearest layer patch > 60 degrees. displacementMedialAxis : Inserting points on patch inlet if angle to nearest layer patch > 60 degrees. displacementMedialAxis : Inserting points on patch outlet if angle to nearest layer patch > 60 degrees. displacementMedialAxis : Inserting points on patch lowerWall if angle to nearest layer patch > 60 degrees. displacementMedialAxis : Inserting points on patch upperWall if angle to nearest layer patch > 60 degrees. displacementMedialAxis : Smoothing normals in interior ... Iteration 0 residual 0.0953276 Layer addition iteration 0 -------------------------- Determining displacement for added points according to pointNormal ... Detected 21 points with point normal pointing through faces. Reset displacement at 21 points to average of surrounding points. displacementMedialAxis : Smoothing using Medial Axis ... ------------------------------------------------------- Primary job terminated normally, but 1 process returned a non-zero exit code.. Per user-direction, the job has been aborted. ------------------------------------------------------- -------------------------------------------------------------------------- mpirun detected that one or more processes exited with non-zero status, thus causing the job to be terminated. The first process to do so was: Process name: [[26524,1],1] Exit code: 145 -------------------------------------------------------------------------- So I am guessing it may be due to the boundary layer. Does anyone know what happen? Thanks!! Here is my snappyHexMeshDict: Code:
castellatedMesh true; snap true; addLayers true; geometry { figure { type triSurfaceMesh; file "figure.stl"; } refinementBox { type searchableBox; min ( 30 205.267 90); max ( 700 1760 1850); } }; castellatedMeshControls { maxLocalCells 1000000; maxGlobalCells 30000000; minRefinementCells 15; maxLoadUnbalance 0.10; nCellsBetweenLevels 3; features ( { file "figure.eMesh"; level 4; } ); refinementSurfaces { figure { level (4 4); patchInfo { type wall; inGroups (figureGroup); } } } resolveFeatureAngle 20; refinementRegions { refinementBox { mode inside; levels ((1E15 4)); } } locationInMesh (402.1 1802.1 1002.3) ; allowFreeStandingZoneFaces true; } snapControls { nSmoothPatch 5; tolerance 2.0; nSolveIter 40; nRelaxIter 5; nFeatureSnapIter 10; implicitFeatureSnap false; explicitFeatureSnap true; multiRegionFeatureSnap false; } addLayersControls { relativeSizes true; layers { //"(lowerWall|figure).*" "figure.*" { nSurfaceLayers 3; } } expansionRatio 1.1; firstLayerThickness 0.3; minThickness 0.03; nGrow 0; featureAngle 175; slipFeatureAngle 60; nRelaxIter 5; nSmoothSurfaceNormals 1; nSmoothNormals 3; nSmoothThickness 10; maxFaceThicknessRatio 0.5; maxThicknessToMedialRatio 0.3; minMedianAxisAngle 90; nBufferCellsNoExtrude 0; nLayerIter 15; } meshQualityControls { #include "meshQualityDict" } writeFlags ( scalarLevels layerSets layerFields ); mergeTolerance 1e-6; // ************************************************************************* // |
|
July 7, 2019, 17:18 |
|
#2 |
Member
Rishikesh
Join Date: Apr 2016
Posts: 63
Rep Power: 10 |
Hi,
Did you figure out what causes the above error? I noticed you encountered the same problem with a pisoFoam where you were able to run with reduced timestep. But did you find the source of this problem, because my simulation is running at quite small timestep size (maxCo = 0.2) and yet it crashes in parallel. Just prior to crash, the Co value suddenly shoots up to ~8-10 from 0.05-0.1... This problem doesn't happen when running a serial case. regards, rishi Last edited by mrishi; July 7, 2019 at 19:29. |
|
Tags |
boundary layer, mpirun error, snappyhexmesh |
|
|
Similar Threads | ||||
Thread | Thread Starter | Forum | Replies | Last Post |
what is wrong with the mpirun parameter -mca ? | donno | OpenFOAM | 7 | February 2, 2023 22:12 |
mpirun hangup.. can anyone help how to fix mpirun issues. | prameelar | OpenFOAM | 12 | February 16, 2022 17:23 |
MPIrun Problem with FoamJob Workaround | kaszt | OpenFOAM Running, Solving & CFD | 3 | October 4, 2018 13:55 |
mpirun unable to find SU2_PRT | Apollinaris | SU2 Installation | 1 | May 10, 2017 06:31 |
using mpirun | EmadTandis | OpenFOAM Running, Solving & CFD | 1 | December 4, 2016 15:29 |