Yes, thanks. Strongly support your jobs!!
|
Quick note: I've adapted the official bug fix to my repository, but there is a somewhat small discrepancy in the results achieved with the function object versus my custom utility.
The reason is likely because I'm using the "rho" from the thermodynamic model, while the function object is using the one from the turbulence model. I have not yet changed this, because it's a bit complicated to do so. There is an issue open for fixing this, so for anyone reading this, feel free to contribute: https://github.com/wyldckat/yPlusLES...sible/issues/1 |
Just comment here:
In openfoam, to correctly predict the y+, we need the the velocity gradient at the wall snGrad. Actually, this is just just a difference using the deltaCoeff and velocity difference, so in LES, if the first cell is very far from the wall, the y+ that OF give will not be very accurate. This is my personal understanding, Please comment as well if what I am saying is not reasonable. OFFO Quote:
|
Hi OFFO,
Quote:
The thing is that if the cell centre is very far away, then the y+ value will probably be very large as well, which would make it a bit redundant to know if the y+ is 1002 or 1100, since... well, it's clearly still in the region where we can use the wall function. And in such a case, it probably means that your mesh needs some fine tuning. But there are a few other problems associated with this:
edit: my guess is that those bug reports won't be closed, unless there is explicit sponsorship for those fixes to be implemented. Best regards, Bruno |
Thank you for your comments.
For wall function in RANS for mut (mutUWallFunction): Since log law will be used for the first cell near the wall, then we must make that y lie in the log-law region (y+>30); For wall function in LES for muSsgs (USpaldingWallFunction): Since this wall law is semi-emperical formula to fit the linear law and log law, so this law can be used in whole inner turbulent boundary layer, i.e. viscous sublayer, buffer layer and log law regions. So for this case, y+ is only reqiured to lie in inner layer, instead of only log law. About the way to calculate the y+, actually, in the implementations for MutUWallFunction Code:
OpenFOAM-2.1.x / src / turbulenceModels / compressible / RAS / derivedFvPatchFields / wallFunctions / mutWallFunctions / mutUWallFunction / mutUWallFunctionFvPatchScalarField.C Code:
tmp<scalarField> mutUWallFunctionFvPatchScalarField::calcYPlus OFFO Quote:
|
Hi OFFO,
Problem is that most (if not all) implementations will require the distance of the centre of the cell (or at least I think it is) to be accurate enough, otherwise all y+ calculations will be too different from the "real" values. I took a quick look at where y+ was used in the source code:
With some effort, it's possible to adapt the code made available on the second bug report: http://www.openfoam.org/mantisbt/view.php?id=968 - the idea would be to copy-paste-rename the turbulence models you want to use and modify them to use this new wall distance calculation, instead of the standard one. Best regards, Bruno |
What you said is correct. The discussion with you always make me learn lots of knowledge about Openfoam. Thank you.
OFFO |
Hello
This post has been a great help for me.I am currently working in of version 2.3.0.I tried to calculate y+ for compressible flow but it is still asking for nuSgs file. I tried the method mentioned above of compiling the yPlusCompreesibleWLES file with wmake however i got the error message: Code:
Making dependency list for source file yPlusLESCompressible.C Kindly help me to resolve the same Pratik |
Does it mean that the versions of y+ utility and your openfoam used are not compatiable with each other?
Quote:
|
Thank you for your reply
I tried to follow the instructions given in the site to calculate yPlusLES for compressible flows: https://github.com/wyldckat/yPlusLES...ble/tree/of21x However I got the error message mentioned in my earlier post when i used wmake. My OpenFoam version is 2.3.0 and i guess the file is not compatible with the version i use. Pratik |
Greetings to all!
@Pratik: I've updated the instructions: https://github.com/wyldckat/yPlusLES...swcompressible Best regards, Bruno |
Quote:
|
We have made a bug report to openfoam. Is this updated in the latest version of yPlus, like in your version?
Quote:
|
yPlusLES for compressible flow is available for openFoam 2.3.0 and is given in the website : https://github.com/wyldckat/yPlusLES...swcompressible
|
Quote:
|
if you have turbulence off, how can you have the LES?
Quote:
|
Hi All,
Thanks for the discussion of the y+ treatment, following the thread from the start has been really helpful for me. I do have a couple of questions though, hence why I resurrected this thread... I am running OF 2.4.0 on Ubuntu 14.04. 1. I tried to run yPlusLES on the throttle tutorial for cavitatingFoam but I got the error keyword transportModel is undefined in dictionary "/home/dan/OpenFOAM/dan-2.4.0/run/tutorials/multiphase/cavitatingFoam/les/throttle/constant/transportProperties" file: /home/dan/OpenFOAM/dan-2.4.0/run/tutorials/multiphase/cavitatingFoam/les/throttle/constant/transportProperties from line 18 to line 64. From function dictionary::lookupEntry(const word&, bool, bool) const in file db/dictionary/dictionary.C at line 442. Is this due to the change in structure for multiphase transport properties dict between 2.4.0 and previous OF versions? should I log this as a bug? 2. The -compressible option has been removed, what is the correct useage now? Do I need to follow the instructions from wyldckat for v2.3.0 with some modifications to use the different transportProperties dict? Thanks, Dan Edit: I found the problem (it should have been obvious to me earlier but anyway) is that the utility does not handle a multiphase definition of nu / mu. A work around is to assume that all cells close to the wall are alpha = 1 and at the end of the run, temporarily rem out the vapour phase definitions in the transportProperties file. Unfortunately in my case this assumption does not always hold true so now looking at making my own utility, I will post back if I have any success :) |
@Dan: Quick answers:
|
All times are GMT -4. The time now is 18:07. |