How to Decipher Floating Point Exception

NotDrJeff · December 10, 2020, 13:21

Hello,

Heads up, I have no idea what I'm doing

.

I am very new to OpenFOAM and CFD in general. I am experimenting with a case which was designed for incompressible flow. I am trying to adapt the case to a compressible flow and solve it using rhoPimpleFoam.

I have been troubleshooting various errors as I go. Most of the errors that I get are clearly described and I can fix them.

However, I have now run into a floating point exception error:

Code:

Starting time loop

Courant Number mean: 0 max: 0
deltaT = 6e-05
Time = 6e-05

PIMPLE: iteration 1
#0  Foam::error::printStack(Foam::Ostream&) at ??:?
#1  Foam::sigFpe::sigHandler(int) at ??:?
#2  ? in /lib/x86_64-linux-gnu/libpthread.so.0
#3  Foam::divide(Foam::Field<double>&, Foam::UList<double> const&, Foam::UList<double> const&) at ??:?
#4  Foam::operator/(Foam::UList<double> const&, Foam::UList<double> const&) at ??:?
#5  Foam::diagonalSolver::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  Foam::fvMesh::solve(Foam::fvMatrix<double>&, Foam::dictionary const&) const at ??:?
#9  ? in ~/OpenFOAM/OpenFOAM-v2006/platforms/linux64GccDPInt32Opt/bin/rhoPimpleFoam
#10  __libc_start_main in /lib/x86_64-linux-gnu/libc.so.6
#11  ? in ~/OpenFOAM/OpenFOAM-v2006/platforms/linux64GccDPInt32Opt/bin/rhoPimpleFoam
Floating point exception (core dumped)

The solver does not seem to even begin solving anything, so I can't see what the numbers were doing. This makes me think my initial and boundary conditions are at fault, but I have checked over them and tried a few different set ups to no avail.

I am not here to get a specific solution to my problem (though that would be nice). Rather, I want to learn how to make sense of these errors. I can't figure out what any of it means. Are these OpenFOAM errors? C++ errors? bash errors?
Where do they come from and where can I find a guide to deciphering not just this problem, but similar errors in future?

Any help appreciated.

Thank you!

CFD-HSNR · December 11, 2020, 07:47

From my experience, I can tell you that such error messages occur when the solver is supposed to perform mathematical operations that are not possible, such as the classic case of division by zero.

Finding the trigger of the problem is often not trivial. In my case, physically meaningless boundary conditions were often the problem. But it could also be the mesh.

I would advise you to check your boundary conditions and your mesh. For the latter, the application checkMesh is highly recommended.

December 10, 2020, 13:21	How to Decipher Floating Point Exception	#1
NotDrJeff New Member Jeffrey Johnston Join Date: Oct 2020 Location: Belfast, Northern Ireland Posts: 21 Rep Power: 5	Hello, Heads up, I have no idea what I'm doing . I am very new to OpenFOAM and CFD in general. I am experimenting with a case which was designed for incompressible flow. I am trying to adapt the case to a compressible flow and solve it using rhoPimpleFoam. I have been troubleshooting various errors as I go. Most of the errors that I get are clearly described and I can fix them. However, I have now run into a floating point exception error: Code: Starting time loop Courant Number mean: 0 max: 0 deltaT = 6e-05 Time = 6e-05 PIMPLE: iteration 1 #0 Foam::error::printStack(Foam::Ostream&) at ??:? #1 Foam::sigFpe::sigHandler(int) at ??:? #2 ? in /lib/x86_64-linux-gnu/libpthread.so.0 #3 Foam::divide(Foam::Field<double>&, Foam::UList<double> const&, Foam::UList<double> const&) at ??:? #4 Foam::operator/(Foam::UList<double> const&, Foam::UList<double> const&) at ??:? #5 Foam::diagonalSolver::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 Foam::fvMesh::solve(Foam::fvMatrix<double>&, Foam::dictionary const&) const at ??:? #9 ? in ~/OpenFOAM/OpenFOAM-v2006/platforms/linux64GccDPInt32Opt/bin/rhoPimpleFoam #10 __libc_start_main in /lib/x86_64-linux-gnu/libc.so.6 #11 ? in ~/OpenFOAM/OpenFOAM-v2006/platforms/linux64GccDPInt32Opt/bin/rhoPimpleFoam Floating point exception (core dumped) The solver does not seem to even begin solving anything, so I can't see what the numbers were doing. This makes me think my initial and boundary conditions are at fault, but I have checked over them and tried a few different set ups to no avail. I am not here to get a specific solution to my problem (though that would be nice). Rather, I want to learn how to make sense of these errors. I can't figure out what any of it means. Are these OpenFOAM errors? C++ errors? bash errors? Where do they come from and where can I find a guide to deciphering not just this problem, but similar errors in future? Any help appreciated. Thank you!

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
icoFoam floating point exception (8)	leizhao512	OpenFOAM Running, Solving & CFD	7	November 1, 2018 11:43
A floating point exception has occurred: floating point exception [Overflow].	starlight	STAR-CCM+	4	May 4, 2016 09:08
A floating point exception - SEM Model	yansheng	STAR-CCM+	1	April 4, 2016 04:57
Floating point exception from twoPhaseEulerFoam	openfoammaofnepo	OpenFOAM Running, Solving & CFD	1	March 19, 2016 13:56
Floating point exception (core dumped) for GAMG solver	yuhou1989	OpenFOAM Running, Solving & CFD	2	March 24, 2015 19:28

December 11, 2020, 07:47		#2
CFD-HSNR New Member Max Join Date: Apr 2020 Location: Germany Posts: 8 Rep Power: 6	From my experience, I can tell you that such error messages occur when the solver is supposed to perform mathematical operations that are not possible, such as the classic case of division by zero. Finding the trigger of the problem is often not trivial. In my case, physically meaningless boundary conditions were often the problem. But it could also be the mesh. I would advise you to check your boundary conditions and your mesh. For the latter, the application checkMesh is highly recommended. hogsonik and NotDrJeff like this.