|
[Sponsors] |
How to solve/go around a Floating point exception |
|
LinkBack | Thread Tools | Search this Thread | Display Modes |
November 4, 2022, 08:27 |
How to solve/go around a Floating point exception
|
#1 |
New Member
Faris Al-Jamal
Join Date: Jul 2022
Posts: 1
Rep Power: 0 |
Dear All,
Since 2 months, I'm having an issue with running a URANS simulation whenever the mesh exceeds 100k. It is a 2D case with dynamicMesh (library: libfvMotionSolvers and solver: solidBody) and AMI. The case should run for 3 sec, but it always stops between 0.02 - 0.075 sec, with the following text: mpirun noticed that process rank 12 with PID **** on node *** exited on signal 8 (Floating point exception). Surprisingly, in my case the solution doesnt blow up, i.e diverges, it just simply stops working. After searching a lot about it, I found some saying that there might be a bug, but I can not be sure. Anyway it is really important for me to make it work. I tried the following solutions but non worked: Trying different meshing techniques. (By checking the mesh no issues come up) Solution schemes:
without. Use a different version of OpenFOAM both (.org and .com). Use large and small timeStep, fixed or variable. Add limitations on Courant Number. Run the solution in serial. Note: The solution for finer meshes (about 400k) worked normally when I run the case without dynamicMesh,i.e non roatiting AMI, or when using the library (libsixDoFRigidBodyMotion.so) and (sixDoFRigidBodyMotion) solver. A solution or suggestions are highly appreciated. Another question: Is there a trick to use the libsixDoFRigidBodyMotion library, but ensure a constant rotational speed (Omega) ? Thanks in advance |
|
Tags |
ami, floating point exception, urans, vawt |
|
|
Similar Threads | ||||
Thread | Thread Starter | Forum | Replies | Last Post |
icoFoam floating point exception (8) | leizhao512 | OpenFOAM Running, Solving & CFD | 7 | November 1, 2018 12:43 |
A floating point exception has occurred: floating point exception [Overflow]. | starlight | STAR-CCM+ | 4 | May 4, 2016 10:08 |
A floating point exception - SEM Model | yansheng | STAR-CCM+ | 1 | April 4, 2016 05:57 |
Floating point exception from twoPhaseEulerFoam | openfoammaofnepo | OpenFOAM Running, Solving & CFD | 1 | March 19, 2016 14:56 |
Floating point exception (core dumped) for GAMG solver | yuhou1989 | OpenFOAM Running, Solving & CFD | 2 | March 24, 2015 20:28 |