|November 21, 2013, 09:30||
orthogonal cells marked as nonOrthogonal
Join Date: Aug 2010
Location: Groningen, The Netherlands
Posts: 216Rep Power: 10
I have some troubles with cells which are marked as nonOrthogonal
but are according to my interpretation perfectly orthogonal.
checkMesh says maxOrth: 75.xxx with 10k cells in a mesh of 3.1M cells.
I'm using LTSInterfoam in a more or less simple channel flow with a ship.
The cells causing troubles are created with a refinementBox in sHM
If somebody could give me an explanation to that phenomena and maybe
an explanation on how I can avoid them, would be great.
See attached some pictures which should illustrate the problem:
If you have further questions or need more information let me know
|January 22, 2014, 10:24||
Join Date: Feb 2012
Posts: 173Rep Power: 14
Only the cells that lie between different levels of refinement are affected, right? This is caused by the hanging nodes introduced by the mesher in order to achieve the refinement.
Check this post checkMesh
The cells fall into checkMesh's definition of a non-orthogonal cell although the cell - to the user - seems perfectly orthogonal.
|Thread||Thread Starter||Forum||Replies||Last Post|
|No layers in a small gap||bobburnquist||OpenFOAM Native Meshers: snappyHexMesh and Others||6||August 26, 2015 09:38|
|Import netgen mesh to OpenFOAM||hsieh||Open Source Meshers: Gmsh, Netgen, CGNS, ...||32||September 13, 2011 05:50|
|snappyHexMesh won't work - zeros everywhere!||sc298||OpenFOAM Native Meshers: snappyHexMesh and Others||2||March 27, 2011 21:11|
|snappyHexMesh aborting||Tobi||OpenFOAM Native Meshers: snappyHexMesh and Others||0||November 10, 2010 04:23|
|physical boundary error!!||kris||CD-adapco||2||August 3, 2005 00:32|