saving . . . saved Error while running solver "icoFoam" has been deleted. Error while running solver "icoFoam" has been hidden .
Error while running solver "icoFoam"
Title
Question
This is the Error that i am getting after running solver "solver". Solver crashes after some time.


Courant Number mean: 32.084 max: 1334.68
#0  Foam::error::printStack(Foam::Ostream&) at ??:?
#1  Foam::sigFpe::sigHandler(int) at ??:?
#2  ? in "/lib/x86_64-linux-gnu/libc.so.6"
#3  Foam::symGaussSeidelSmoother::smooth(Foam::word const&, Foam::Field<double>&, Foam::lduMatrix const&, Foam::Field<double> const&, Foam::FieldField<Foam::Field, double> const&, Foam::UPtrList<Foam::lduInterfaceField const> const&, unsigned char, int) at ??:?
#4  Foam::symGaussSeidelSmoother::smooth(Foam::Field<double>&, Foam::Field<double> const&, unsigned char, int) const at ??:?
#5  Foam::smoothSolver::solve(Foam::Field<double>&, Foam::Field<double> const&, unsigned char) const at ??:?
#6  ? in "/opt/openfoam8/platforms/linux64GccDPInt32Opt/bin/icoFoam"
#7  ? in "/opt/openfoam8/platforms/linux64GccDPInt32Opt/bin/icoFoam"
#8  ? in "/opt/openfoam8/platforms/linux64GccDPInt32Opt/bin/icoFoam"
#9  ? in "/opt/openfoam8/platforms/linux64GccDPInt32Opt/bin/icoFoam"
#10  __libc_start_main in "/lib/x86_64-linux-gnu/libc.so.6"
#11  ? in "/opt/openfoam8/platforms/linux64GccDPInt32Opt/bin/icoFoam"

OpenFOAM-version-7 Simulating-Hagen-Poiseuille-flow-through-a-pipe-in-OpenFOAM 09-10 min 30-40 sec 26-09-20, 3:11 p.m. Shubhanshu_rai

Answers:

Have you changed the Kinematic viscosity?
Fluid velocity depends on viscosity and velocity is in the courant no calculation.
Due to high courant no. You are getting error.

Thanks,
Divyesh
26-09-20, 3:41 p.m. divyesh7


courant number is exceeding 1, rather it is shooting to unsustainably high for the solver to continue calculations.
this means that either the mesh dimensions are incorrect by order of magnitude of 100 (mesh is 100 times smaller), making the grid size samller
OR the time step mentioned in the controlDict is very large.

Lowering timestep or making the mesh coarser should solve this problem.

26-09-20, 3:46 p.m. ameyak2310


Log-in to answer to this question.