Thank you!
|
Quote:
If you get this behaviour again, try adding/reducing the number of cells in one direction with 1. I use snappy mostly for internal flows and then the patches doesnt matter. Thats why. you can safely change the patches to whatever you want. |
Thanks again!
|
2 Attachment(s)
Hello Niklas!
After getting the nicer mesh I am trying to simulate the wind pressure on my Umbrella... I am getting crazy results on this Umb Patch [See attached pic] although the calculations seem correct if took a slice [attaches a pic as well] So I used a faceZone and created two patches out of it ... the problem continues ... this is how the boundary file will look like after modification: Code:
7 [Q]Is there another way to do that? Please see this thread for more details.. http://www.cfd-online.com/Forums/ope...nd-tunnel.html ________________________________________________ [P.s]: How serious are the errors in checkMesh: Code:
<<Writing 21 conflicting points to set nonManifoldPoints Code:
***Max skewness = 6.6003492, 8 highly skew faces detected Really appreciate your advice |
Here I have uploaded my Meshing Case and Simulation Case
http://dl.dropbox.com/u/32336583/How...Patches.tar.gz Please take a look Thanks! |
Hi!
I am using snappyHexMesh with OF2.2 but the program never finish to do the snapping. When it is snapping I always get a warning message: "FOAM Warning : Displacement () at mesh point '*' coord () points through the surrounding patch faces". After that the program moves the mesh. Sometimes the program is not successful and writes: "Did not succesfully snap mesh. Giving up." I've tried a lot of combinations with the parameters inside the snapyHexMeshDict and I've also changed the blockMeshDict as niklas said, without success. The .eMesh archive is correct. I've created an .obj file and I've seen it in paraview. Here you have an example: Code:
FOAM Warning : Displacement (-0.02266843 0.001091078 0.002192178) at mesh point 5161178 coord (1007.063 -66.16199 -0.003698507) points through the surrounding patch faces Code:
vertices Code:
// Which of the steps to run Thanks! David |
Quote:
|
2 Attachment(s)
Of course!! I forgot to attach the geometry.
Here you have the complete geometry and a detail. |
Hi,
It seems that I solved it. The problem was that the mesh was written in mm, so it was 1 km length. I was going to scale it after doing snappyHexMesh but It's better to do it before. It seems that the little displacements of the mesh was 1000 times bigger, and snappy tried to reduce this displacements. |
Quote:
Hi, friend, I met the same problem as above. Could you explain it clearer? Thank you so much!Which should it be corrected? Regards, Jackie |
Hi jackeyhust,
In my case this error was mainly for three (four) reasons: 1. You didn't use the explicit feature to snap (check new releases of OF 2.2.0) 2. You have to play with the feature angle. 3. The snap did't work correctly because it used to give up. You should check your log file and observe the end of the morph iterations. If it's not working it will write 'giving up'. If you have this problem you have to relax the quality parameters and decrease the number of nFeatureSnapIter iterations. EDIT: 4.Snappy doesn't like the blockMesh input. You should do the cells as hexagonal as possible. You can also play with the number of cells. Hope this helps ;) |
Quote:
it works now! But I still use explicit feature. I have read about the new features. But they said "The explicit method offers greater control and, from our experience, provides slightly better feature conformation. The implicit method has the advantage of being fully automated." So what's your idea about this? Thank you so much for the reply! Jackie |
@Jackie
Hello Jackie
I am also having the problem that snappyHexMesh gives up with out finishing the snapping. It would be helpful how could you solve the problem. I am meshing a centrifugal blower. I have a MRF included. as mentioned previously I checked/played some parameters like resolveFeatureAngle and all .. but could not get a good mesh. It completely misses the geometry... !! Also in the log of snappy Hex mesh it says the given point is found in the cell -1 in region 0 of 4 ... !! Is that a problem... !! |
Hi, niklas. What is the trick to use snappyHexMesh? I have similar problem where snap doesn't work nicely. The problem is posted here http://www.cfd-online.com/Forums/ope...tml#post480610
Quote:
|
All times are GMT -4. The time now is 23:48. |