CFD Online Logo CFD Online URL
Home > Forums > Software User Forums > OpenFOAM > OpenFOAM Running, Solving & CFD

Erroneous Courant Number in FOAM log?

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

LinkBack Thread Tools Display Modes
Old   April 29, 2014, 22:45
Default Erroneous Courant Number in FOAM log?
John Wang
Join Date: Mar 2009
Location: Singapore
Posts: 72
Rep Power: 10
cwang5 is on a distinguished road
Hi guys,

I'm trying to use the adjustTimeStep option in controDict to run my LES simulation. However, the courant number reported at run time is so high that OpenFOAM was forced to constantly reduce the time step size until it hits ~1e-30 and the whole simulation just crashed. I revised the simulation to run on fixed time step, and was getting the following message in my log:
Courant Number mean: 0.0042170848 max: 136.39391
Time = 75.642

DILUPBiCG:  Solving for Ux, Initial residual = 0.00032185865, Final residual = 3.2946399e-08, No Iterations 1
DILUPBiCG:  Solving for Uy, Initial residual = 0.00029752553, Final residual = 3.1410567e-08, No Iterations 1
DILUPBiCG:  Solving for Uz, Initial residual = 0.00066511108, Final residual = 7.6629127e-08, No Iterations 1
GAMG:  Solving for p, Initial residual = 0.0046290147, Final residual = 7.3302722e-05, No Iterations 2
GAMG:  Solving for p, Initial residual = 7.3305549e-05, Final residual = 9.6448053e-07, No Iterations 13
time step continuity errors : sum local = 7.9685318e-13, global = 8.7932007e-14, cumulative = 1.3817586e-10
ExecutionTime = 53373.4 s  ClockTime = 53430 s
which reported a maximum courant number of ~135 for every time step. However, the value reported by the Co utility showed that the maximum courant number is ~0.04 when I post processed the data:
Time = 75
    Reading phi
    Calculating incompressible Co
Co max : 0.032720504


Time = 76
    Reading phi
    Calculating incompressible Co
Co max : 0.032659777

Is it a problem with the adjustTimeStep calculation of the courant number that's causing the issue? And what can I do to be able to run the simulation with adjustTimeStep turned on so I can save on simulation time?


EDIT: I should add that the simulation was stable for the entire simulation even with maxCo reported at ~135.
EDIT2: I looked into OpenFOAM source code, and the Courant number in Co is calculated using
while it's calculated in CourantNo.C with
The biggest difference is the extra rho(phi)().internalField() term, which accounts for compressibility as stated in CourantNo.H
        //- Return 1 if the flux field is volumetric i.e. incompressible flow?, otherwise return rho
        //  from the database
        tmp<volScalarField> rho(const surfaceScalarField& p) const;
everything other difference is between reading from a output database file vs reading from memory at the time of computing as far as I can tell.
On a side note, I ran the same simulation using a finer mesh (2/3 of original grid size), and obtained significantly lower Courant number of ~0.1 in FOAM log, which enabled me to turn on adjustTimeStep.

Last edited by cwang5; April 30, 2014 at 07:19.
cwang5 is offline   Reply With Quote


Thread Tools
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 On
Pingbacks are On
Refbacks are On

Similar Threads
Thread Thread Starter Forum Replies Last Post
Mesh Refinement Luiz Eduardo Bittencourt Sampaio (Sampaio) OpenFOAM Mesh Utilities 42 January 8, 2017 13:55
whats the cause of error? immortality OpenFOAM Running, Solving & CFD 11 April 22, 2014 12:32
BlockMeshmergePatchPairs hjasak OpenFOAM Native Meshers: blockMesh 11 August 15, 2008 07:36
IcoFoam parallel woes msrinath80 OpenFOAM Running, Solving & CFD 9 July 22, 2007 02:58
Axisymmetrical mesh Rasmus Gjesing (Gjesing) OpenFOAM Native Meshers: blockMesh 10 April 2, 2007 14:00

All times are GMT -4. The time now is 20:40.