CFD Online Logo CFD Online URL
www.cfd-online.com
[Sponsors]
Home > Forums > Software User Forums > OpenFOAM > OpenFOAM Running, Solving & CFD

One probable cause of high bounding epsilon & k values

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

Like Tree1Likes
  • 1 Post By nero235

Reply
 
LinkBack Thread Tools Search this Thread Display Modes
Old   April 9, 2015, 05:02
Lightbulb One probable cause of high bounding epsilon & k values
  #1
Member
 
Sebastian W.
Join Date: Nov 2012
Location: Saxony, Germany
Posts: 43
Rep Power: 15
nero235 is on a distinguished road
Send a message via ICQ to nero235
Hello friends,

I would like to share some experience regarding the problems which may or may not occur when running OpenFOAM multiphase solvers on sHM meshes with activated turbulence models. This isn't necessarily limited to multiphase solvers but can also occur when using single-phase solvers like simpleFoam etc.

Here are some boundary conditions to reproduce the problem
  • Mesh has to generated with sHM (version irrelevant)
  • Cells at the wall have to be finer compared to the internal cell size (as seen in the left part of the attached image). It doesn't matter however how many cells are in between the layers (nCellsBetweenLevels)
  • Activated turbulence: k-epsilon models
  • Solver version <= 2.2.2 (haven't tested recent versions)
As seen in the left domain where there are different cell sizes, I assume that the transition between the cells is critical and the cause of the high bounding values of k & epsilon.

As far as the question about numerical schemes goes I can say: it doesn't matter! I tested every scheme combination there is:
  • upwind (divSchemes, k & epsilon)
  • Gauss linearLimited 1 (divSchemes, k & epsilon)
  • cellMDLimited leastSquares 1 (gradSchemes, default)
  • limited 0.333 (laplacian & snGradSchemes, default)
I've also tested different k-epsilon models. It may help for some time using limiting schemes and the realizableKE model, but the probability is very high that the solver still crashes because of the bounding values or a ever rising Co which will result in a decreasing time step.

I tested the same case on both meshes as seen below. The result was that the solver always crashed with the left mesh with "bounding" warnings at each time step and the case with the right mesh continued to run, with only one "bounding" warning which was at the beginning of the simulation.

As far as I am concerned, the only solution to the described problem is to use one cell size for the complete domain. I am open to other tips and I hope that this post helps someone.

Regards, Sebastian
Attached Images
File Type: jpg screen.jpg (41.8 KB, 134 views)
Devin063 likes this.
nero235 is offline   Reply With Quote

Old   April 9, 2015, 08:23
Default
  #2
Member
 
Join Date: Sep 2014
Location: Germany
Posts: 88
Rep Power: 13
TobM is on a distinguished road
Hi Sebastian,

have you checked y+ in the first near wall cell layer? The standard wall functions don't like a y+< 30 to 50. I observed very strange behaviour in the near wall region in cases where the near wall resolution was too high.
Do you use wall functions at all?

Just a few thoughts about your problem, maybe you have already considered these points.

Last edited by TobM; April 9, 2015 at 08:24. Reason: typo
TobM is offline   Reply With Quote

Old   April 9, 2015, 08:37
Default
  #3
Member
 
Sebastian W.
Join Date: Nov 2012
Location: Saxony, Germany
Posts: 43
Rep Power: 15
nero235 is on a distinguished road
Send a message via ICQ to nero235
Quote:
Originally Posted by TobM View Post
Hi Sebastian,

have you checked y+ in the first near wall cell layer? The standard wall functions don't like a y+< 30 to 50. I observed very strange behaviour in the near wall region in cases where the near wall resolution was too high.
Do you use wall functions at all?

Just a few thoughts about your problem, maybe you have already considered these points.
Yes, I have checked the y+ values. Problem is when solving multiphase flow the y+ can't be pin-pointed to one specific value. It ranges in my case from 0.7 to 210.
It's acceptable for the air to use the Low-Re wall treatment, since the kinematic viscosity is high. When considering the fluids (liquid metals & slag in my case) the kinematic viscosity drops dramatically and therefore the y+ is rather high. Since I don't assume the gas velocities to be in the range of the liquids I used wall functions (High-Re wall treatment).

I guess there is no way to stay out of a specific range in my case.
nero235 is offline   Reply With Quote

Reply

Thread Tools Search this Thread
Search this Thread:

Advanced Search
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 Off
Pingbacks are On
Refbacks are On


Similar Threads
Thread Thread Starter Forum Replies Last Post
Calculation of k and epsilon freezes Nigirim OpenFOAM Running, Solving & CFD 1 November 14, 2012 08:52
epsilon and K blowing up. sivakumar OpenFOAM Running, Solving & CFD 1 October 25, 2012 05:50
Values of epsilon Gearb0x OpenFOAM Running, Solving & CFD 2 May 20, 2010 13:36
Bounding epsilon and K with rasInterFoam openfoam_user OpenFOAM Running, Solving & CFD 0 October 23, 2008 09:48
Multicomponent fluid Andrea CFX 2 October 11, 2004 06:12


All times are GMT -4. The time now is 01:34.