Defective snapping produced deviation
1 Attachment(s)
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: Attachment 24331 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. |
Done!
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 : Code:
Correcting 2-D mesh motion ...done |
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 |
sHM
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. |
All times are GMT -4. The time now is 10:52. |