|
[Sponsors] |
January 25, 2013, 11:42 |
Mesh Problem
|
#1 |
New Member
Med
Join Date: Apr 2012
Location: Tunisia
Posts: 10
Rep Power: 14 |
Dear enGridusers,
I am a newbie with engrid and I have tried to generate a mesh with the command " create prismatic boundary layer " But I encountered a problem with this alert message ' Netgen stopped with the following error: Stop meshing since surface mesh not consistent ' Here is attached the debug file. Any help would be most welcome !! Best regards, |
|
January 28, 2013, 07:04 |
|
#2 |
Senior Member
Oliver Gloth
Join Date: Mar 2009
Location: Todtnau, Germany
Posts: 121
Rep Power: 17 |
Hello,
your surface mesh is, indeed, not consistent. Where does this mesh come from? Did you create it with enGrid, or did you import it from somewhere else? A little bit more info would be required to be able to help. Cheers, Oliver |
|
January 28, 2013, 10:01 |
|
#3 |
New Member
Med
Join Date: Apr 2012
Location: Tunisia
Posts: 10
Rep Power: 14 |
Hello Olivier,
I have already solved the problem.Infact, there were some missing entities (surfaces) when I exported the geometry from Gmsh to engrid. Actually, now, I am facing a new problem, after meshing and exporting the geometry to OpenFOAM, I did a quick check with the utility checkMesh and I got 4 errors. What do you think about my mesh ? Here is attached the log file 'logMesh' . Also, I have some questions about engrid cause I am using the 1.4x version and I encountered some bug. Should I use other previous versions ? Thanks, Have a nice day, Mohamed |
|
January 28, 2013, 16:30 |
|
#4 |
Senior Member
Oliver Gloth
Join Date: Mar 2009
Location: Todtnau, Germany
Posts: 121
Rep Power: 17 |
Hello Mohamed,
the checkMesh error you are getting are a bit unusual for a pure prism/tet mesh, but it is difficult to tell what is going on without seeing the mesh or geometry. It is important, that you assign different boundary codes to different geometric features in order to keep the feature edges and to get a nice boundary layer mesh. For example, a cube should consist of 6 boundary codes (patches). If you create your surface mesh with enGrid, your are more or less forces to follow this rule, otherwise you end up with "round" edges. If you discover a bug or problem in 1.4, or the release-1.4 branch on GIT, feel free to post a bug report on GitHUB. The official release is 1.4, but the release-1.4 branch shouldn't be far away from that. Cheers, Oliver |
|
January 29, 2013, 07:07 |
|
#5 |
New Member
Med
Join Date: Apr 2012
Location: Tunisia
Posts: 10
Rep Power: 14 |
Hello Oliver,
I will try to follow your advice then I will let you know about the results. Best regards, Mohamed |
|
February 1, 2013, 17:01 |
|
#6 |
New Member
Med
Join Date: Apr 2012
Location: Tunisia
Posts: 10
Rep Power: 14 |
Olivier,
Your advice helps me ... now I have a good mesh ( no errors with checkMesh ) by assigning for each patch a code. I really enjoyed using engrid !! Thanks, Mohamed HADDAR |
|
|
|
Similar Threads | ||||
Thread | Thread Starter | Forum | Replies | Last Post |
Dynamic Mesh Problem. | Tom Clark | FLUENT | 10 | June 21, 2021 05:27 |
Gambit problems | Althea | FLUENT | 22 | January 4, 2017 04:19 |
Icemcfd 11: Loss of mesh from surface mesh option? | Joe | CFX | 2 | March 26, 2007 19:10 |
Convergence problem when ustructured mesh is used. | SangJin Ryu | Siemens | 3 | October 5, 2000 21:26 |
Mesh | Mignard | FLUENT | 2 | March 22, 2000 06:12 |