CFD Online Discussion Forums

CFD Online Discussion Forums (https://www.cfd-online.com/Forums/)
-   OpenFOAM Meshing & Mesh Conversion (https://www.cfd-online.com/Forums/openfoam-meshing/)
-   -   [snappyHexMesh] mpirun error on with addLayer ON (https://www.cfd-online.com/Forums/openfoam-meshing/217230-mpirun-error-addlayer.html)

Jinjolee May 4, 2019 13:35

mpirun error on with addLayer ON
 
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
--------------------------------------------------------------------------

I have another case that meshed the exact same model and ran the same snappyHexMesh expect the addLayers was OFF, and it ran perfectly fine.
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;


// ************************************************************************* //

Really appreciate your help!!

mrishi July 7, 2019 17:18

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


All times are GMT -4. The time now is 02:30.