# convergence problems with omega in kOmegaSSTSAS

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

 May 18, 2017, 14:19 convergence problems with omega in kOmegaSSTSAS #1 New Member   Lukas Lebovitz Join Date: Mar 2017 Location: Zürich, Switzerland Posts: 25 Rep Power: 2 Dear Foamers I'm trying to do a SAS simulation (LES model = kOmegaSSTSAS) for a flow around a cube. My domain is 100m long x 80m wide x 80m tall. My cube has size 10m x 10m x 10m. I have a shear flow with 4.5m/s on z=10m. I have a blockmesh with more than 4million cells. yPlus values with wallfunctions is in the range of 50-150 though I'm not sure if I can trust this if my omega does not converge. I'm using timesteps of 0.01s. My Initial and Boundary Conditions are: k Code: ```internalField uniform 0.3; boundaryField { inlet { type fixedValue; value uniform 0.1; } outlet { type zeroGradient; } ground { type kqRWallFunction; value uniform 1e-5; } top { type symmetryPlane; } side1 { type cyclic; } side2 { type cyclic; } cube { type kqRWallFunction; value uniform 1e-5; } }``` omega Code: ```internalField uniform 1; boundaryField { inlet { type fixedValue; value uniform 1; } outlet { type zeroGradient; } ground { type omegaWallFunction; value uniform 10; } top { type symmetryPlane; } side1 { type cyclic; } side2 { type cyclic; } cube { type omegaWallFunction; value uniform 10; } }``` If I set pimpleFoam to piso-mode omega will quickly diverge to infinity. Im using limitedlinear01 1 for both k and omega in fvSchemes. k and omega will also sometimes go below zero (as low as ~ -10) so that I get bounding k and omega errors. I tried using the pimple algorithm with up to 50 inner Loops but omega will still not converge. I have set turbOnFinalIterOnly to false so it does indeed solve omega on every iteration. Anyone knows what else I can try?

 May 18, 2017, 15:33 #2 Member   Joshua Join Date: Dec 2016 Location: St. Louis, Missouri Posts: 91 Rep Power: 2 lukas.lebo, A time step of 0.01 might be to large. Take a look at what your Courant number is and if that is blowing up. Joshua

 May 18, 2017, 16:12 #3 New Member   Lukas Lebovitz Join Date: Mar 2017 Location: Zürich, Switzerland Posts: 25 Rep Power: 2 My mean Co is below 0.1 and my max Co fluctuates between 0.5 and 2.0 with an average of ~1.3 ... It'd be hilarious if max Co < 1.0 is required for all cells at all times. (I'm sampling statistics for over 2100s) I made the same simulation with LES (oneEqEddy) and had no problems whatsoever except I did not resolve the viscous sublayer at small yPlus. Which is the reason I want to compare it to a SAS case with wallfunctions. I'm also doing it with an hilariously fine mesh in LES which will take over 2 months to complete on a HPC cluster (but results will not be available anytime soon ... ).

May 19, 2017, 01:11
#4
Senior Member

Uwe Pilz
Join Date: Feb 2017
Location: Leipzig, Germany
Posts: 306
Rep Power: 4
Quote:
 Originally Posted by lukas.lebo My mean Co is below 0.1 and my max Co fluctuates between 0.5 and 2.0 with an average of ~1.3 ... It'd be hilarious if max Co < 1.0 is required for all cells at all times. (I'm sampling statistics for over 2100s)
Dear Lukas,

I like to mention two things.
1) Usually the maximum Courant number appears in the most critical parts of the geometry. These parts are the starting point of divergence. If the first few round converge, you may set the writeIntercal to timestep and look what happens. This is very instructive.
2) Even at simple geometries a Courant number of 1 or even 0.5 is not advising. It may be that the simulation converges, but the time needed for that may be longer than necessary. Please keep in mind: The pimple method makes a prediction step which needs to be corrected. It is out of sense to have a large prediction step and then need a lot of time for correcting it. I found that Max Courant numbers of 0.1 or even below lead to remarkably shorter wall clock times for simulation.

Even if the simulation converges, there are signs of a too large Courant number. During my simulations I observe dte Co with the help of awk:
Code:
`pimpleFoam | awk -f pr.awk`
The print pr.awk file contains:
Code:
```/Courant/ { mean=\$4;max=\$6;}
/^Time/ {print "Time:",\$3, ", Co(MW, Max):", mean,max}```
If you observe time steps which take much longer than the steps before and after, the you observe an accumulation of deviations, which needs a long time to be corrected. Depending on your settings, the max Co number exceeds the setting for this step. If you observe such tings, reduce the maxCo.

Don't be afraid about the wall time for running the simulation: It will be shorter.

If your simulation has stabilized, you may increase the maxCo on the fly. openFoam detects this and uses the new value with the next time step. There was rarely a need for applying this correction, however: What you gain with the time step you loose with the correction.
__________________
Uwe Pilz
--
Sie ahnen nicht, wieviel Poesie in der Berechnung
einer Logarithmentafel enthalten ist (Carl Friedrich Gauß)

 Thread Tools Display Modes Linear Mode

 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 OffTrackbacks are On Pingbacks are On Refbacks are On Forum Rules

 Similar Threads Thread Thread Starter Forum Replies Last Post drdet FloEFD, FloWorks & FloTHERM 12 January 22, 2015 05:44 IngmarVanDijk FLUENT 6 November 12, 2014 11:50 santiagomarquezd OpenFOAM Running, Solving & CFD 0 October 28, 2014 11:53 jeremy FLUENT 7 May 30, 2002 06:41 Emilien FLUENT 3 May 3, 2002 08:43

All times are GMT -4. The time now is 14:00.