CFD Online Logo CFD Online URL
www.cfd-online.com
[Sponsors]
Home > Forums > Software User Forums > OpenFOAM > OpenFOAM Meshing & Mesh Conversion

[snappyHexMesh] snappyHexMesh and checkMesh - different definitions of skewness

Register Blogs Community New Posts Updated Threads Search

Like Tree1Likes
  • 1 Post By cibanez

Reply
 
LinkBack Thread Tools Search this Thread Display Modes
Old   May 9, 2017, 09:21
Default snappyHexMesh and checkMesh - different definitions of skewness
  #1
Senior Member
 
Yuehan
Join Date: Nov 2012
Posts: 142
Rep Power: 14
wc34071209 is on a distinguished road
Hi everybody,

It seems that snappyHexMesh and checkMesh calculate face skewness in a different way.


snappyHexMesh output

Code:
Checking final mesh ...
Checking faces in error :
    non-orthogonality > 80  degrees                        : 0
    faces with face pyramid volume < 1e-30                 : 0
    faces with concavity > 80  degrees                     : 0
    faces with skewness > 4   (internal) or 20  (boundary) : 0
    faces with interpolation weights (0..1)  < 0.005       : 0
    faces with volume ratio of neighbour cells < 0.001     : 0
    faces with face twist < 0.001                          : 152
    faces on cells with determinant < 0.0001                : 54
Finished meshing with 206 illegal faces (concave, zero area or negative cell pyramid volume)
Finished meshing in = 98.52 s.
End

checkMesh output

Code:
Checking geometry...
    Overall domain bounding box (-0.600453913 -0.000453508017 -6.17837081e-08) (0.60016445 2.4400002 2.46000011)
    Mesh (non-empty, non-wedge) directions (1 1 1)
    Mesh (non-empty) directions (1 1 1)
    Boundary openness (-1.48156865e-16 8.02340479e-17 -2.54456316e-16) OK.
    Max cell openness = 3.16296583e-16 OK.
    Max aspect ratio = 26.777507 OK.
    Minimum face area = 3.60752727e-08. Maximum face area = 0.00704660078.  Face area magnitudes OK.
    Min volume = 1.40396368e-10. Max volume = 0.000584855605.  Total volume = 7.1436757.  Cell volumes OK.
    Mesh non-orthogonality Max: 79.940617 average: 12.8038228
   *Number of severely non-orthogonal (> 70 degrees) faces: 329.
    Non-orthogonality check OK.
  <<Writing 329 non-orthogonal faces to set nonOrthoFaces
    Face pyramids OK.
 ***Max skewness = 4.39520581, 1 highly skew faces detected which may impair the quality of the results
  <<Writing 1 skew faces to set skewFaces
    Coupled point location match (average 0) OK.

Failed 1 mesh checks.

End
wc34071209 is offline   Reply With Quote

Old   May 9, 2017, 11:00
Default
  #2
Senior Member
 
akidess's Avatar
 
Anton Kidess
Join Date: May 2009
Location: Germany
Posts: 1,377
Rep Power: 30
akidess will become famous soon enough
I'm guessing the skew face that snappyHexMesh reports lies on the boundary.
__________________
*On twitter @akidTwit
*Spend as much time formulating your questions as you expect people to spend on their answer.
akidess is offline   Reply With Quote

Old   May 10, 2017, 05:36
Default
  #3
Senior Member
 
Yuehan
Join Date: Nov 2012
Posts: 142
Rep Power: 14
wc34071209 is on a distinguished road
Quote:
Originally Posted by akidess View Post
I'm guessing the skew face that snappyHexMesh reports lies on the boundary.
Yes, you are right. But do you know why this happens?
wc34071209 is offline   Reply With Quote

Old   August 30, 2023, 06:12
Default
  #4
New Member
 
Cristóbal
Join Date: Jan 2022
Location: Sweden
Posts: 17
Rep Power: 4
cibanez is on a distinguished road
Hi,

It happens because when checkMesh checks for face skewness it only uses one threshold value to issue the warning. That is skewThreshold_ = 4, which is hardcoded.

You can take a look at https://develop.openfoam.com/Develop...eck.C#L565-630 to see that checkMesh doesn't distinguish between internal or boundary faces to write out the warning. At the beginning of this file you will also find the hardcoded variables used as threshold values. For instance it can be seen that nonOrthThreshold_ = 70 degrees for non-orthogonality.

It could then be a good practice to lower maxBoundarySkewness in your meshQualityDict to 4 when creating the mesh with SHM to be sure to avoid checkMesh warnings.
rmaries likes this.
cibanez is offline   Reply With Quote

Reply


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
[snappyHexMesh] error checkMesh after run snappyHexMesh Hemmati OpenFOAM Meshing & Mesh Conversion 5 November 20, 2016 03:42
[snappyHexMesh] Able to run snappyHexMesh in parallel on local machine but unable to run on linux clu abhinav2601 OpenFOAM Meshing & Mesh Conversion 1 January 26, 2015 06:42
[mesh manipulation] checkMesh Erros after refineMesh mgdenno OpenFOAM Meshing & Mesh Conversion 10 October 14, 2014 06:16
checkMesh Errors after refineMesh mgdenno OpenFOAM 0 July 30, 2012 22:39
[snappyHexMesh] snappyHexMesh not snapping perfectly to surface and failing checkMesh Greg Givogue OpenFOAM Meshing & Mesh Conversion 5 February 28, 2011 12:43


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