|
[Sponsors] |
[snappyHexMesh] Defective snapping produced deviation |
|
LinkBack | Thread Tools | Search this Thread | Display Modes |
August 12, 2013, 10:00 |
Defective snapping produced deviation
|
#1 |
Member
|
I think the problem has principle character.
I've tried a lot of modifications of some basic sHM dictionaries but if somebody need my source files i will attach it. The problem: problem.jpg Questions: 1. Did somebody met similar problem with snapping procedure? 2. What did you do with it to eliminate deviation from stl surface or feature edge? Thanks.
__________________
practice makes perfect |
|
August 13, 2013, 04:50 |
Done!
|
#2 |
Member
|
I've analyzed the problem successfully!
1. To prevent such behavior of sHM the mesh should not have 'empty' patches. So if you need prism layer at the symmetryPlane, you should change patch type only on final stage of your meshing process. 2. So when you have 'empty' patches you will get such messages: Code:
Correcting 2-D mesh motion--> FOAM Warning : From function twoDPointCorrector::twoDPointCorrector(const polyMesh& mesh, const vector& n) in file twoDPointCorrector/twoDPointCorrector.C at line 152 the number of vertices in the geometry is odd - this should not be the case for a 2-D case. Please check the geometry. --> FOAM Warning : From function twoDPointCorrector::twoDPointCorrector(const polyMesh& mesh, const vector& n) in file twoDPointCorrector/twoDPointCorrector.C at line 164 The number of points in the mesh is not equal to twice the number of edges normal to the plane - this may be OK only for wedge geometries. Please check the geometry or adjust the orthogonality tolerance. Code:
Correcting 2-D mesh motion ...done
__________________
practice makes perfect |
|
August 20, 2013, 02:18 |
|
#3 |
Member
Miro
Join Date: Jan 2013
Location: Europe
Posts: 51
Rep Power: 13 |
oscillation on a surface probably means you overdid it with your smoothing operations.
If your surface is not smooth you should use a better (finer) stl, and not smooth so much. If I understand correctly (i didn't go trough the whole thread) you're meshing an airfoil in 3D? If so, you should check out the dictionary for sHM in incompressible/pimpleDyFoam/wingmotion. cheers - miro |
|
August 20, 2013, 02:25 |
sHM
|
#4 | |
Member
|
Quote:
But i think it's a vexed question. I mean that in case when one or two patches has 'empty' type sHM trying to 'syncronize' mesh. So points are aligned but in many cases point cloud is not regular, so it's produce additional iterations to find a good alignment. At the end user has waved mesh.
__________________
practice makes perfect |
||
|
|
Similar Threads | ||||
Thread | Thread Starter | Forum | Replies | Last Post |
[snappyHexMesh] SHM not snapping to some surfaces | Swift | OpenFOAM Meshing & Mesh Conversion | 13 | January 4, 2016 01:56 |
[snappyHexMesh] Snapping problem, non orthogonal faces | Zephiro88 | OpenFOAM Meshing & Mesh Conversion | 7 | April 17, 2015 02:56 |
temperature dependent deviation | hebeldebel | STAR-CCM+ | 7 | July 30, 2014 10:44 |
[snappyHexMesh] Snapping not enough (even with surfaceFeatureExtract) | ironclad | OpenFOAM Meshing & Mesh Conversion | 1 | November 8, 2013 02:58 |
Standard deviation for every time step | shyam | OpenFOAM Running, Solving & CFD | 3 | April 19, 2012 07:39 |