Limit on warnings during snapping stage

I am runnign a sHM case, which has ended up in a log file (snappyHexMesh step) of beyond 2Gb size, due to warnings during the snapping stage, like this:

    Did not find surface near face centre (0.0843533 0.0788768 0.0969448)
--> FOAM Warning :
    From function void Foam::snappySnapDriver::calcNearestFace(Foam::label, cons
t indirectPrimitivePatch&, const scalarField&, Foam::vectorField&, Foam::vectorF
ield&, Foam::labelList&) const
    in file snappyHexMeshDriver/snappySnapDriverFeature.C at line 331

Is it possible to limit the number of warning outputs?

assigned to @Mattijs

mentioned in commit a71841d9

mentioned in commit f94c0c38

Limited to first 100 warnings. Does this need to be 1000? 1000000?

I believe 100 is good.

But how about we leave it to specification in SHMDict ? as debug?

added bug label

The warnings might actually come from incorrect indexing. If the case

• has faceZone
• has processors with differing levels of refinement
• it might index the incorrect search distance and hence not find any attraction.

mentioned in commit 57c06b72

mentioned in commit d7c6dbc3

mentioned in commit a8f73dc0

closed via commit b9de83cf

mentioned in commit b9de83cf