CFD Online Discussion Forums

CFD Online Discussion Forums (
-   OpenFOAM Running, Solving & CFD (
-   -   Guidance on reading an error message (

laurent25 January 24, 2008 11:54

Dear OpenFOAM community, I
Dear OpenFOAM community,

I am playing with the icoDyMFoam solver. I looked at the tutorial and I am now trying to build a simple 2D case: a box with a lid on the top moving up and down.
When running it, I have the following error message:

laurent@laurent-desktop:~/OpenFOAM/laurent-1.4.1/run/test2D$ icoDyMFoam . estuary
| ========= | |
| \ / F ield | OpenFOAM: The Open Source CFD Toolbox |
| \ / O peration | Version: 1.4.1 |
| \ / A nd | Web: |
| \/ M anipulation | |

Exec : icoDyMFoam . estuary
Date : Jan 24 2008
Time : 15:27:59
Host : laurent-desktop
PID : 9404
Root : /home/laurent/OpenFOAM/laurent-1.4.1/run/test2D
Case : estuary
Nprocs : 1
Create time

Create mesh for time = 0

Selecting dynamicFvMesh dynamicMotionSolverFvMesh
Selecting motion solver: velocityComponentLaplacian

--> FOAM FATAL ERROR : Not implemented#0 Foam::error::printStack(Foam: in "/home/laurent/OpenFOAM/OpenFOAM-1.4.1/lib/linuxGccDPOpt/"
#1 Foam::error::abort() in "/home/laurent/OpenFOAM/OpenFOAM-1.4.1/lib/linuxGccDPOpt/"
#2 Foam::defaultFvPatchField<double>::defaultFvPatchF ield(Foam::fvPatch const&, Foam::DimensionedField<double,> const&) in "/home/laurent/OpenFOAM/OpenFOAM-1.4.1/lib/linuxGccDPOpt/"
#3 Foam::fvPatchField<double>::addpatchConstructorToT able<foam::defaultfvpatchfield <double> >::New(Foam::fvPatch const&, Foam::DimensionedField<double,> const&) in "/home/laurent/OpenFOAM/OpenFOAM-1.4.1/lib/linuxGccDPOpt/"
#4 Foam::fvPatchField<double>::New(Foam::word const&, Foam::fvPatch const&, Foam::DimensionedField<double,> const&) in "/home/laurent/OpenFOAM/OpenFOAM-1.4.1/applications/bin/linuxGccDPOpt/icoDyMFoam "
#5 Foam::GeometricField<double,>::GeometricBoundaryFi eld::GeometricBoundaryField(Fo am::fvBoundaryMesh const&, Foam::DimensionedField<double,> const&, Foam::List<foam::word> const&) in "/home/laurent/OpenFOAM/OpenFOAM-1.4.1/lib/linuxGccDPOpt/"
#6 Foam::GeometricField<double,>::GeometricField(Foam ::IOobject const&, Foam::fvMesh const&, Foam::dimensioned<double> const&, Foam::List<foam::word> const&) in "/home/laurent/OpenFOAM/OpenFOAM-1.4.1/lib/linuxGccDPOpt/"
#7 Foam::velocityComponentLaplacianFvMotionSolver::ve locityComponentLaplacianFvMoti onSolver(Foam::polyMesh const&, Foam::Istream&) in "/home/laurent/OpenFOAM/OpenFOAM-1.4.1/lib/linuxGccDPOpt/"
#8 Foam::motionSolver::adddictionaryConstructorToTabl e<foam::velocitycomponentlapla cianfvmotionsolver>::New(Foam::polyMesh const&, Foam::Istream&) in "/home/laurent/OpenFOAM/OpenFOAM-1.4.1/lib/linuxGccDPOpt/"
#9 Foam::motionSolver::New(Foam::polyMesh const&) in "/home/laurent/OpenFOAM/OpenFOAM-1.4.1/lib/linuxGccDPOpt/"
#10 Foam::dynamicMotionSolverFvMesh::dynamicMotionSolv erFvMesh(Foam::IOobject const&) in "/home/laurent/OpenFOAM/OpenFOAM-1.4.1/lib/linuxGccDPOpt/"
#11 Foam::dynamicFvMesh::addIOobjectConstructorToTable <foam::dynamicmotionsolverfvme sh>::New(Foam::IOobject const&) in "/home/laurent/OpenFOAM/OpenFOAM-1.4.1/lib/linuxGccDPOpt/"
#12 Foam::dynamicFvMesh::New(Foam::IOobject const&) in "/home/laurent/OpenFOAM/OpenFOAM-1.4.1/lib/linuxGccDPOpt/"
#13 main in "/home/laurent/OpenFOAM/OpenFOAM-1.4.1/applications/bin/linuxGccDPOpt/icoDyMFoam "
#14 __libc_start_main in "/lib/tls/i686/cmov/"
#15 Foam::regIOobject::readIfModified() in "/home/laurent/OpenFOAM/OpenFOAM-1.4.1/applications/bin/linuxGccDPOpt/icoDyMFoam "

From function defaultFvPatchField<type>::defaultFvPatchField(con st fvPatch& p, const DimensionedField<type,>& iF)
in file fields/fvPatchFields/basic/default/defaultFvPatchField.C at line 50.

FOAM aborting

Aborted (core dumped)

Could someone give me some guidance on how to interpret this message?

thanks very much in advance


gschaider January 24, 2008 12:16

The text after FOAM FATAL ERRO
The text after FOAM FATAL ERROR is a situation specific error message (in your case: the method exists, but is not properly implemented)

The stuff with #<nr> is a stack-trace ( (If you're using a Debug-version of OF it might even show you the files and line numbers)

After that follows the source-file and the line number that caused the error.

saf5029 June 16, 2008 10:05

Do you recall what you changed
Do you recall what you changed when you got this error, I just got an identical one and am having trouble fixing it.



suredross June 18, 2008 07:32

hi, i am compiling a solver(m
i am compiling a solver(modified icoFoam)to solve this equation:

dimensionedScalar k=q*l/(U0*mu);
solve (
(Ux = -(k*fvc::grad(psi)))
//(like a boundary condition)
and keep getting this error:

SOURCE=jxnFoam.C ; g++ -m32 -Dlinux -DDP -Wall -Wno-strict-aliasing -Wextra -Wno-unused-parameter -Wold-style-cast -O3 -DNoRepository -ftemplate-depth-40 -I/home/cfd/OpenFOAM/OpenFOAM-1.4.1/src/finiteVolume/lnInclude -IlnInclude -I. -I/home/cfd/OpenFOAM/OpenFOAM-1.4.1/src/OpenFOAM/lnInclude -fPIC -pthread -c $SOURCE -o Make/linuxGccDPOpt/jxnFoam.o
jxnFoam.C: In function 'int main(int, char**)':
jxnFoam.C:115: error: invalid use of void expression
/home/cfd/OpenFOAM/OpenFOAM-1.4.1/src/finiteVolume/lnInclude/initContinuityErrs. H:38: warning: unused variable 'cumulativeContErr'
make: *** [Make/linuxGccDPOpt/jxnFoam.o] Error 1

any help will be appreciated.


ngj June 18, 2008 07:47

Assume psi is a scalar, then g
Assume psi is a scalar, then grad(psi) is a vector which cannot be equal to a scalar, which I assumme Ux is.

Further I believe you need '==' and not just '=' when setting up equations. Further no 'fvm::' command is used, thus no variable to solve for is specified.

I you want qualified help, you need to post definition of the different variables etc, otherwise you will receive guesses just as this on.

- Niels

suredross June 18, 2008 09:29

hi Niels good to hear from yo
hi Niels
good to hear from you again.
i am trying to impose a boundary condition(the Helmholtz-smoluchowski equation) on the walls of my case after the calculation for an electrical field has elapsed.this is to see the effect the field will have on the velocity at the cells next(immediately)to the boundary.
what will be the best way to go about this?any suggestions are welcome


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