[syavash]

Dear All,

When I try to run the tutorial of channel395 with OF 1812 using GAMG (default), the simulation crashes with the following error:

PIMPLE: iteration 1
smoothSolver:  Solving for Ux, Initial residual = 0.00317098, Final residual = 9.6554e-07, No Iterations 1
smoothSolver:  Solving for Uy, Initial residual = 0.003193, Final residual = 9.5391e-07, No Iterations 1
smoothSolver:  Solving for Uz, Initial residual = 0.00303762, Final residual = 9.22401e-07, No Iterations 1
#0  Foam::error::printStack(Foam::Ostream&) at ??:?
#1  Foam::sigFpe::sigHandler(int) at ??:?
#2  ? in /lib64/libpthread.so.0
#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 ??:?
#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 ??:?
#5  Foam::GAMGSolver::solve(Foam::Field<double>&, Foam::Field<double> const&, unsigned char) const at ??:?
#6  Foam::fvMatrix<double>::solveSegregated(Foam::dictionary const&) at ??:?
#7  Foam::fvMatrix<double>::solveSegregatedOrCoupled(Foam::dictionary const&) at ??:?
#8  ? at ??:?
#9  __libc_start_main in /lib64/libc.so.6
#10  ? at ??:?
Floating point exception

I tried to run another tutorial (airfoil2D) which uses GAMG as default for pressure. However, it crashes similarly. I tried PCG for the first case and it was fine though. I have no idea what may be wrong here! Any help?

Syavash

[syavash]

I wonder NOT a single person run into a similar problem with OF v1812? Any idea?

[phi4ever]

I got a similar error, same floating point exception. I resolved this by changing the relaxation factors to slow down the convergence. In my case the results were blowing up, which led to the floating point exception.