|
[Sponsors] |
Changing to cyclic gives Floating point Exeptions |
![]() |
|
LinkBack | Thread Tools | Search this Thread | Display Modes |
![]() |
![]() |
#1 |
Member
Anders Utnes
Join Date: May 2017
Location: Norway
Posts: 34
Rep Power: 9 ![]() |
Hi
I have a LES SA channel flow that converges fine using non-cyclic boundary conditions, but when I change them to cyclicAMI I get a floating point exeption error. Anyone have any ideas regarding what can be done about this? Error at first timestep: Code:
Starting time loop Time = 1e-05 Courant Number mean: 0.340063 max: 11.085 smoothSolver: Solving for Ux, Initial residual = 1, Final residual = 7.96896e-06, No Iterations 4 smoothSolver: Solving for Uy, Initial residual = 1, Final residual = 9.76301e-06, No Iterations 4 smoothSolver: Solving for Uz, Initial residual = 1, Final residual = 6.46279e-06, No Iterations 4 #0 Foam::error::printStack(Foam::Ostream&) in "/opt/OpenFOAM/OpenFOAM-v1612+/platforms/linux64GccDPInt32Opt/lib/libOpenFOAM.so" #1 Foam::sigFpe::sigHandler(int) in "/opt/OpenFOAM/OpenFOAM-v1612+/platforms/linux64GccDPInt32Opt/lib/libOpenFOAM.so" #2 ? in "/lib64/libc.so.6" #3 Foam::divide(Foam::Field<double>&, double const&, Foam::UList<double> const&) in "/opt/OpenFOAM/OpenFOAM-v1612+/platforms/linux64GccDPInt32Opt/lib/libOpenFOAM.so" #4 Foam::tmp<Foam::GeometricField<double, Foam::fvPatchField, Foam::volMesh> > Foam::operator/<Foam::fvPatchField, Foam::volMesh>(Foam::dimensioned<double> const&, Foam::tmp<Foam::GeometricField<double, Foam::fvPatchField, Foam::volMesh> > const&) in "/opt/OpenFOAM/OpenFOAM-v1612+/platforms/linux64GccDPInt32Opt/bin/pisoFoam" #5 ? in "/opt/OpenFOAM/OpenFOAM-v1612+/platforms/linux64GccDPInt32Opt/bin/pisoFoam" #6 __libc_start_main in "/lib64/libc.so.6" #7 ? in "/opt/OpenFOAM/OpenFOAM-v1612+/platforms/linux64GccDPInt32Opt/bin/pisoFoam" Floating point exception Code:
U: inlet { type fixedValue; value uniform (1 0 0); } outlet { type inletOutlet; inletValue uniform (0 0 0); value uniform (1 0 0); } P: inlet { type zeroGradient; } outlet { type fixedValue; value uniform 0; } k: inlet { type fixedValue; value uniform 13.5; } outlet { type inletOutlet; inletValue uniform 13.5; value uniform 13.5; } nut: type calculated; value uniform 0; } outlet { type calculated; value uniform 0; } nutilda: inlet { type fixedValue; value uniform 0.000002; } outlet { type fixedValue; value uniform 0; } Code:
All Fields: inlet { type cyclicAMI; } outlet { type cyclicAMI; } |
|
![]() |
![]() |
![]() |
![]() |
#2 |
Member
Anders Utnes
Join Date: May 2017
Location: Norway
Posts: 34
Rep Power: 9 ![]() |
// Bumpeti bump bump
![]() |
|
![]() |
![]() |
![]() |
![]() |
#3 |
Senior Member
cyln
Join Date: Jul 2016
Posts: 102
Rep Power: 10 ![]() |
Hello,
have you figured this problem out? I am having the same problem with cyclicAMI boundary condition Instead, if I use symmetry, it does not give me any floating point error. |
|
![]() |
![]() |
![]() |
![]() |
#4 |
Member
Anders Utnes
Join Date: May 2017
Location: Norway
Posts: 34
Rep Power: 9 ![]() |
I've changed a lot of things since I posted this, and I dont get the problem any longer. I cant remeber what fixed it thou.
Post your boundary file for me? I think the problem may have been there. |
|
![]() |
![]() |
![]() |
![]() |
#5 |
Senior Member
cyln
Join Date: Jul 2016
Posts: 102
Rep Power: 10 ![]() |
Here is my 0/U file:
Code:
internalField uniform (1 1 1); boundaryField { INLET1 { type fixedValue; value nonuniform List<vector> 2673 ( ( 17.4495 0.0000 0.0000 ) ... ... ( 4.7022 0.0000 0.0000 ) ) ; } INLET2 { type zeroGradient; } SIDE11 { type cyclicAMI; } SIDE22 { type cyclicAMI; } CYL { type slip; } OUTLET { type zeroGradient; } SURFACE1 { type noSlip; } SURFACE2 { type noSlip; } DISCHARGE { type noSlip; } PLUG { type noSlip; } } Code:
dimensions [0 2 -2 0 0 0 0]; internalField uniform 1.0; boundaryField { INLET1 { type zeroGradient; } INLET2 { type totalPressure; p0 uniform 100000; value uniform 100000; gamma 1.4; } SIDE11 { type cyclicAMI; } SIDE22 { type cyclicAMI; } CYL { type zeroGradient; } OUTLET { type fixedValue; value uniform 1.0; } SURFACE1 { type zeroGradient; } SURFACE2 { type zeroGradient; } DISCHARGE { type zeroGradient; } PLUG { type zeroGradient; } } Code:
10 ( INLET1 { type patch; nFaces 2673; startFace 20264662; } INLET2 { type patch; nFaces 13206; startFace 20267335; } CYL { type wall; inGroups 1(wall); nFaces 65099; startFace 20280541; } OUTLET { type patch; nFaces 47929; startFace 20345640; } SURFACE2 { type wall; inGroups 1(wall); nFaces 12944; startFace 20393569; } SURFACE1 { type wall; inGroups 1(wall); nFaces 13221; startFace 20406513; } DISCHARGE { type wall; inGroups 1(wall); nFaces 436; startFace 20419734; } PLUG { type wall; inGroups 1(wall); nFaces 4376; startFace 20420170; } SIDE11 { type cyclicAMI; inGroups 1(cyclicAMI); nFaces 215211; startFace 20424546; matchTolerance 0.001; transform rotational; neighbourPatch SIDE22; rotationAxis (1 0 0); rotationCentre (0 0 0); } SIDE22 { type cyclicAMI; inGroups 1(cyclicAMI); nFaces 215315; startFace 20639757; matchTolerance 0.001; transform rotational; neighbourPatch SIDE11; rotationAxis (1 0 0); rotationCentre (0 0 0); } ) |
|
![]() |
![]() |
![]() |
![]() |
#6 |
Member
Anders Utnes
Join Date: May 2017
Location: Norway
Posts: 34
Rep Power: 9 ![]() |
In my case I think it was incorrect use of "translational" in the "transform" section of the boundary file. Obviously this may not apply to you since you use "rotational". You may want to doublecheck that this BC is correctly applied however.
And Group 1 seems to include both the walls and the cyclic part. Not sure if that's ever used, but if it is that seems like a possible errorsource. Sorry that I could not be of more help. |
|
![]() |
![]() |
![]() |
![]() |
#7 |
New Member
Johnson Liu
Join Date: Apr 2021
Location: Hong Kong
Posts: 5
Rep Power: 5 ![]() |
I am having the same problem too. No problems for "symmetry" condition, but the "floating point exception" arises when changed to cyclicAMI. I am using KOmegaSST model.
|
|
![]() |
![]() |
![]() |
![]() |
#8 | |
New Member
Johnson Liu
Join Date: Apr 2021
Location: Hong Kong
Posts: 5
Rep Power: 5 ![]() |
Quote:
|
||
![]() |
![]() |
![]() |
![]() |
#9 | |
New Member
Johnson Liu
Join Date: Apr 2021
Location: Hong Kong
Posts: 5
Rep Power: 5 ![]() |
Quote:
Hope this will be helpful for others. |
||
![]() |
![]() |
![]() |
|
|
![]() |
||||
Thread | Thread Starter | Forum | Replies | Last Post |
icoFoam - Floating point exception (core dumped) | File | OpenFOAM Running, Solving & CFD | 26 | March 6, 2021 04:26 |
[snappyHexMesh] How to define to right point for locationInMesh | Mirage12 | OpenFOAM Meshing & Mesh Conversion | 7 | March 13, 2016 14:07 |
pimpleDyMFoam constantly giving floating point exception and solution divergence | fedvasu | OpenFOAM Running, Solving & CFD | 0 | November 28, 2013 00:53 |
[snappyHexMesh] determining displacement for added points | CFDnewbie147 | OpenFOAM Meshing & Mesh Conversion | 1 | October 22, 2013 09:53 |
Floating point error and divergence detected | aannjj | FLUENT | 0 | July 2, 2013 03:44 |