[Virtual-iCFD]

I encountered the following output message when executing interDyMFoam using version 1.7.0 and I am not sure whether I should continue or kill my run, since my linear and angular velocity becomes "nan" as shown below. If anyone can provide me some useful guideline. I greatly appreciated.

Thank you,

--------------

Create time

Create mesh for time = 0

Selecting dynamicFvMesh dynamicMotionSolverFvMesh
Selecting motion solver: displacementLaplacian
Selecting motion diffusion: inverseDistance
Reading field p_rgh

Reading field alpha1

Reading field U

Reading/calculating face flux field phi

Reading transportProperties

Selecting incompressible transport model Newtonian
Selecting incompressible transport model Newtonian
Selecting turbulence model type RASModel
Selecting RAS turbulence model kEpsilon
kEpsilonCoeffs
{
Cmu 0.09;
C1 1.44;
C2 1.92;
sigmaEps 1.3;
}


Reading g
Calculating field g.h

time step continuity errors : sum local = 0, global = 0, cumulative = 0
GAMGPCG: Solving for pcorr, Initial residual = 0, Final residual = 0, No Iterations 0
time step continuity errors : sum local = 0, global = 0, cumulative = 0
Courant Number mean: 0 max: 0

Starting time loop

Interface Courant Number mean: 0 max: 0
Courant Number mean: 0 max: 0
deltaT = 0.0047619047619
Time = 0.0047619

Centre of mass: (4 0.2 0)
Linear velocity: (nan nan nan)
Angular velocity: (nan nan nan)

[wyldckat]

Greetings Virtual-iCFD,

Originally Posted by Virtual-iCFD

Interface Courant Number mean: 0 max: 0
Courant Number mean: 0 max: 0

Is there any fluid or mesh in your case? The Courant Number shouldn't be zero!

Did you run setFields? Did you redefine setFieldsDict for your new volume mesh? Or maybe it's the mesh that isn't moving the way you expected it to!?

Another possibility is if you built OpenFOAM 1.7.0 with a gcc 4.5.x, then you must either rebuild it with a gcc 4.4.x or update to OpenFOAM 1.7.1!

Best regards,
Bruno

[Virtual-iCFD]

Hi Bruno, thank you for your prompt reply.

It is indeed the volume mesh issue which I overlooked the quality from snappyHexMesh.

After reran snappyHexMesh with new setting and now my case is running just fine. =)