But…after going through the logs, the reason why the runs have failed probably has nothing to do with what I just said.
This is the run log from Run 3:
Time = 1
smoothSolver: Solving for Ux, Initial residual = 0.00550511416334, Final residual = 4.33389007056e-05, No Iterations 2
smoothSolver: Solving for Uy, Initial residual = 0.0136866929635, Final residual = 0.000111771168718, No Iterations 2
smoothSolver: Solving for Uz, Initial residual = 0.0231768809005, Final residual = 0.000159057920557, No Iterations 2
[11] Signal 8 encountered
[11] Going to reraise SIGTERM after writting
[11] Resetting old handlers (just in case)
[11] Unset SIGFPE(8) signal handler
[11] Unset SIGSEGV(11) signal handler
[11] Unset SIGQUIT(3) signal handler
[11] Writing old times:
[11] 1 times to write
[11] Writing current time 1
[11] Printstack:
[11]
[11] #0 Foam::error::printStack(Foam::Ostream&) at ??:?
[11] #1 Foam::writeOldTimesOnSignalFunctionObject::sigHandler(int) at ??:?
[11] #2 in "
[11] #3 Foam::GAMGSolver::scale(Foam::Field<double>&, Foam::Field<double>&, Foam::lduMatrix const&, Foam::FieldField<Foam::Field, double> const&, Foam::UPtrList<Foam::lduInterfaceField const> const&, Foam::Field<double> const&, unsigned char) const at ??:?
[11] #4 Foam::GAMGSolver::Vcycle(Foam::PtrList<Foam::lduMatrix::smoother> const&, Foam::Field<double>&, Foam::Field<double> const&, Foam::Field<double>&, Foam::Field<double>&, Foam::Field<double>&, Foam::Field<double>&, Foam::Field<double>&, Foam::PtrList<Foam::Field<double> >&, Foam::PtrList<Foam::Field<double> >&, unsigned char) const at ??:?
[11] #5 Foam::GAMGSolver::solve(Foam::Field<double>&, Foam::Field<double> const&, unsigned char) const at ??:?
[11] #6 Foam::fvMatrix<double>::solveSegregated(Foam::dictionary const&) at ??:?
[11] #7 Foam::fvMatrix<double>::solve(Foam::dictionary const&) at ??:?
Just my guess: because the solver stopped before the pressure matrix, the divergence probably has nothing to do with the GAME solver but what feeds into the GAME solver…
I downloaded your mesh to run checkMesh, and this is the log…
Checking geometry...
Overall domain bounding box (-9.825 0.000999886032362 -4.16333634234e-17) (18 7.201 7.2)
Mesh (non-empty, non-wedge) directions (1 1 1)
Mesh (non-empty) directions (1 1 1)
Boundary openness (9.62135227303e-17 -5.77334538733e-16 1.19294240686e-15) OK.
***High aspect ratio cells found, Max aspect ratio: 4.94847754682e+94, number of cells 477
<<Writing 477 cells with high aspect ratio to set highAspectRatioCells
Minimum face area = 1.25708398248e-09. Maximum face area = 0.0682384707207. Face area magnitudes OK.
***Zero or negative cell volume detected. Minimum negative volume: -4.07373908016e-09, Number of negative volume cells: 477
<<Writing 477 zero volume cells to set zeroVolumeCells
Mesh non-orthogonality Max: 179.94355699 average: 12.7161686236
*Number of severely non-orthogonal (> 70 degrees) faces: 4226.
***Number of non-orthogonality errors: 1075.
<<Writing 5301 non-orthogonal faces to set nonOrthoFaces
***Error in face pyramids: 3516 faces are incorrectly oriented.
<<Writing 2678 faces with incorrect orientation to set wrongOrientedFaces
***Max skewness = 170.329678972, 685 highly skew faces detected which may impair the quality of the results
<<Writing 685 skew faces to set skewFaces
Coupled point location match (average 0) OK.
With zero or negative volume cells, FVM won’t solve. Should re-mesh.