|
[Sponsors] |
December 6, 2018, 13:34 |
pimpleFoam max Courant number is exceeded
|
#1 |
Member
Join Date: Sep 2018
Posts: 53
Rep Power: 8 |
Hello,
I'm running a transient case with a moving mesh and the max Courant number set to 0.1. At certain times, the velocity field in a small unstructured part of the domain becomes unstable as the quality of the mesh in that region degrades, this is evident in the log file with the max courant number jumping to 0.7. The solver recognizes this and reduces the time step. After that, the instability is damped and the rest of the simulation continues without issue. The problem is, the velocity field at that particular time is ruined, I expected openFoam to ignore the results of that time step, go back and redo the calculations at the previous time step with a smaller delta t value. Would it be possible to implement something like this? |
|
Tags |
adjustable time step, courant number, pimplefoam, variable time step |
|
|
Similar Threads | ||||
Thread | Thread Starter | Forum | Replies | Last Post |
[General] Extracting ParaView Data into Python Arrays | Jeffzda | ParaView | 30 | November 6, 2023 22:00 |
multiphaseEulerFoam high Courant number | Frenk_T | OpenFOAM | 5 | November 24, 2016 04:23 |
multiphaseEulerFoam (OF2.3.0) : Courant number explodes when running in parallel | Mehrez | OpenFOAM Running, Solving & CFD | 10 | May 18, 2016 12:44 |
foam-extend_3.1 decompose and pyfoam warning | shipman | OpenFOAM | 3 | July 24, 2014 09:14 |
compressible flow in turbocharger | riesotto | OpenFOAM | 50 | May 26, 2014 02:47 |