CFD Online Logo CFD Online URL
www.cfd-online.com
[Sponsors]
Home > Forums > Software User Forums > OpenFOAM > OpenFOAM Running, Solving & CFD

Error after running pisoFoam

Register Blogs Members List Search Today's Posts Mark Forums Read

Reply
 
LinkBack Thread Tools Search this Thread Display Modes
Old   November 20, 2012, 03:58
Default Error after running pisoFoam
  #1
New Member
 
okamoto
Join Date: Nov 2012
Posts: 7
Rep Power: 13
kyushusamurai is on a distinguished road
Hi everybody,
I'm a new comer and new user of OpenFoam within just one month. Currently I'm working on simple simulation using a solid block sets on the middle of the domain. After running the simulation I get below errors and I couldn't understand the meaning. Could anybody help me on this matter?Your cooperation is highly appreciated. Thanks in advance.


#0 Foam::error:rintStack(Foam::Ostream&) in "/opt/usrx/OpenFOAM-2.1.1/platforms/linux64GccDPOpt/lib/libOpenFOAM.so"
#1 Foam::sigFpe::sigHandler(int) in "/opt/usrx/OpenFOAM-2.1.1/platforms/linux64GccDPOpt/lib/libOpenFOAM.so"
#2 __restore_rt at sigaction.c:0
#3 void Foam::fvc::surfaceIntegrate<double>(Foam::Field<do uble>&, Foam::GeometricField<double, Foam::fvsPatchField, Foam::surfaceMesh> const&) in "/opt/usrx/OpenFOAM-2.1.1/platforms/linux64GccDPOpt/bin/pisoFoam"
#4 Foam::tmp<Foam::GeometricField<double, Foam::fvPatchField, Foam::volMesh> > Foam::fvc::surfaceIntegrate<double>(Foam::Geometri cField<double, Foam::fvsPatchField, Foam::surfaceMesh> const&) in "/opt/usrx/OpenFOAM-2.1.1/platforms/linux64GccDPOpt/bin/pisoFoam"
#5 Foam::tmp<Foam::GeometricField<double, Foam::fvPatchField, Foam::volMesh> > Foam::fvc::div<double>(Foam::GeometricField<double , Foam::fvsPatchField, Foam::surfaceMesh> const&) in "/opt/usrx/OpenFOAM-2.1.1/platforms/linux64GccDPOpt/bin/pisoFoam"
#6 Foam::fv::gaussLaplacianScheme<double, double>::fvmLaplacian(Foam::GeometricField<double, Foam::fvsPatchField, Foam::surfaceMesh> const&, Foam::GeometricField<double, Foam::fvPatchField, Foam::volMesh> const&) in "/opt/usrx/OpenFOAM-2.1.1/platforms/linux64GccDPOpt/lib/libfiniteVolume.so"
#7 Foam::fv::laplacianScheme<double, double>::fvmLaplacian(Foam::GeometricField<double, Foam::fvPatchField, Foam::volMesh> const&, Foam::GeometricField<double, Foam::fvPatchField, Foam::volMesh> const&) in "/opt/usrx/OpenFOAM-2.1.1/platforms/linux64GccDPOpt/lib/libfiniteVolume.so"
#8 Foam::tmp<Foam::fvMatrix<double> > Foam::fvm::laplacian<double, double>(Foam::GeometricField<double, Foam::fvPatchField, Foam::volMesh> const&, Foam::GeometricField<double, Foam::fvPatchField, Foam::volMesh> const&, Foam::word const&) in "/opt/usrx/OpenFOAM-2.1.1/platforms/linux64GccDPOpt/bin/pisoFoam"
#9 Foam::tmp<Foam::fvMatrix<double> > Foam::fvm::laplacian<double, double>(Foam::GeometricField<double, Foam::fvPatchField, Foam::volMesh> const&, Foam::GeometricField<double, Foam::fvPatchField, Foam::volMesh> const&) in "/opt/usrx/OpenFOAM-2.1.1/platforms/linux64GccDPOpt/bin/pisoFoam"
#10 Foam::tmp<Foam::fvMatrix<double> > Foam::fvm::laplacian<double, double>(Foam::tmp<Foam::GeometricField<double, Foam::fvPatchField, Foam::volMesh> > const&, Foam::GeometricField<double, Foam::fvPatchField, Foam::volMesh> const&) in "/opt/usrx/OpenFOAM-2.1.1/platforms/linux64GccDPOpt/lib/libincompressibleRASModels.so"
#11 Foam::incompressible::RASModels::kEpsilon::correct () in "/opt/usrx/OpenFOAM-2.1.1/platforms/linux64GccDPOpt/lib/libincompressibleRASModels.so"
#12 main in "/opt/usrx/OpenFOAM-2.1.1/platforms/linux64GccDPOpt/bin/pisoFoam"
#13 __libc_start_main in "/lib64/libc.so.6"
#14 Foam::UOPstream::write(char) in "/opt/usrx/OpenFOAM-2.1.1/platforms/linux64GccDPOpt/bin/pisoFoam"
Floating point exception
kyushusamurai is offline   Reply With Quote

Old   November 20, 2012, 04:58
Default
  #2
Member
 
Join Date: Mar 2012
Location: Munich, Germany
Posts: 67
Rep Power: 14
treima is on a distinguished road
Hello,

do you have a division by zero or for any of your variables very high values?

Another thing could be wrong boundary conditions, did you check them?

These two things came in my mind first for a "floating point exception".


regards
treima
treima is offline   Reply With Quote

Old   November 20, 2012, 05:07
Default
  #3
Senior Member
 
Daniel P. Combest
Join Date: Mar 2009
Location: St. Louis, USA
Posts: 621
Rep Power: 0
chegdan will become famous soon enoughchegdan will become famous soon enough
This kind of error can be several things and is indicative of a divide by zero. if you initialize your k or epsilon field with 0 or have a 0 boundary condition...then you will get this. To avoid this, try to change your zero entries to 1e-20 and provide a good initial guess for k and epsilon fields.
chegdan is offline   Reply With Quote

Old   November 20, 2012, 05:14
Default
  #4
New Member
 
okamoto
Join Date: Nov 2012
Posts: 7
Rep Power: 13
kyushusamurai is on a distinguished road
Dear Treima,
Thank for your prompt reply.
1)I dont have any division zero and variables with high values
2)For BC, I set U and p as below;
U;
inlet
{ type fixedValue;
value (12 0 0);
}
outlet
{ type zeroGradient;}
for surrounding walls I set as fixedValue, uniform (0 0 0)

p;
inlet
{type zeroGradient;}
outlet
{type fixedValue;
value uniform 0;
}
for surrounding walls I set as zeroGradient;
I have calculated the values of k and epsilon.
Need your advice on this matter.
kyushusamurai is offline   Reply With Quote

Old   November 20, 2012, 06:11
Default
  #5
Member
 
Join Date: Mar 2012
Location: Munich, Germany
Posts: 67
Rep Power: 14
treima is on a distinguished road
While I donīt know your case exactly I can imagine that your boundary condition for p at outlet, p = 0, might cause some problems.

Which solver do you use? Did you have a look in the tutorials for some example cases and set up your case in a similar form?
treima is offline   Reply With Quote

Old   November 20, 2012, 06:16
Default
  #6
Senior Member
 
Lieven
Join Date: Dec 2011
Location: Leuven, Belgium
Posts: 299
Rep Power: 22
Lieven will become famous soon enough
The boundary conditions for U and p seem ok.

Quote:
I dont have any division zero and variables with high values
The question is not whether there is one or not, the question is really where it is and how it can be found. Foam::sigFpe indicates a floating point exception which almost always indicates a division by zero.

When does the error occur exactly? Is it before the start of the iterations, after a few iterations, or at the end of the full simulation? Or at an other point in time?

Regards,

L
Lieven is offline   Reply With Quote

Old   November 20, 2012, 19:30
Default
  #7
New Member
 
okamoto
Join Date: Nov 2012
Posts: 7
Rep Power: 13
kyushusamurai is on a distinguished road
Dear Lieven,
Thanks for your explanation.
Actually this occurred after a few iterations.
kyushusamurai is offline   Reply With Quote

Reply

Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are Off
Pingbacks are On
Refbacks are On


Similar Threads
Thread Thread Starter Forum Replies Last Post
FV patch problems when running pisoFoam in parallel chrisb OpenFOAM Programming & Development 2 March 21, 2011 05:06
pisoFoam compiling error with OF 1.7.1 on MAC OSX Greg Givogue OpenFOAM Programming & Development 3 March 4, 2011 17:18
Error while running pisoFOAM Virtual-iCFD OpenFOAM Running, Solving & CFD 2 July 20, 2010 02:44
Statically Compiling OpenFOAM Issues herzfeldd OpenFOAM Installation 21 January 6, 2009 09:38
Kubuntu uses dash breaks All scripts in tutorials platopus OpenFOAM Bugs 8 April 15, 2008 07:52


All times are GMT -4. The time now is 19:06.