|
[Sponsors] |
November 9, 2005, 17:14 |
Interior/internal face
|
#1 |
Guest
Posts: n/a
|
I am modelling a turbine blade in a flow. I have created a nice structured mesh around the blade itself, and a triangular paved mesh that covers the rest of the problem. To do this, I subtracted the face that the structured mesh is on from the surrounding face. My problem now is that when I run this in fluent, it sees the boundary between the structured and the unstructured mesh as a wall. I have tried changing the relevant edges to interior, interface and internal, but it just won't let me. Any ideas on what I'm doing wrong?
|
|
November 10, 2005, 09:55 |
Re: Interior/internal face
|
#2 |
Guest
Posts: n/a
|
You talk about faces, so I'm assuming its a 2D model. The problem is that the two faces aren't connected. When you subtract one face from another, now there are two edges where the faces touch. The edges are at the same exact location, but its two separate edges (one for each face). Since the edges aren't connected, there are two sets of nodes, and two sets of elements, and Gambit and Fluent have no way of knowing they are supposed to be attached (you can use the interface option in Fluent... I'll describe that one later). You should have used a split command with the "connected" option turned on. When you do this, only one edge is created, and both faces will share this edge. Since both faces share this edge, the nodes and elements along this edge will be shared when meshing both faces. Since the mesh is now continuous, no BC is needed on this edge, and Gambit will recognize that it's a continuous mesh when it writes the *.msh file. You can go back to Gambit and manually connect the edges. In the face commands, it's on the first row of icons, second from the right... looks like a black plug being plugged-in. In that command, you select the two edges and it will connect them. You might have to fix your mesh after you do this. The other option is using the interface BCs. You have to assign the interface BC on both edges in Gambit. Then in Fluent go to Define->Grid Interfaces and tell Fluent that those two interface BCs are to be one single interface. This introduces a little more error, but if it's not in a high gradient region and as long as there isn't a big change in cell size across the interface, the error should be negligible.
Hope this helps, and good luck, Jason |
|
November 10, 2005, 09:57 |
Re: Interior/internal face
|
#3 |
Guest
Posts: n/a
|
Oh, I meant to mention that all of that works in 3D as well. Just instead of edges being connected, you need edges AND faces connected. There is a connect face option in the face commands that will automatically connect nodes, edges, then faces for you (Gambit always works from the lowest order up... so when you tell it to connect edges, in the background it will connect the nodes first, then the edges). The interfaces also work in 3D.
Jason |
|
November 10, 2005, 16:53 |
Re: Interior/internal face
|
#4 |
Guest
Posts: n/a
|
Brilliant, just got my first converged solution. Thank you so much!
|
|
|
|
Similar Threads | ||||
Thread | Thread Starter | Forum | Replies | Last Post |
[Netgen] Import netgen mesh to OpenFOAM | hsieh | OpenFOAM Meshing & Mesh Conversion | 32 | September 13, 2011 06:50 |
[blockMesh] BlockMeshmergePatchPairs | hjasak | OpenFOAM Meshing & Mesh Conversion | 11 | August 15, 2008 08:36 |
fluent add additional zones for the mesh file | SSL | FLUENT | 2 | January 26, 2008 12:55 |
[blockMesh] Axisymmetrical mesh | Rasmus Gjesing (Gjesing) | OpenFOAM Meshing & Mesh Conversion | 10 | April 2, 2007 15:00 |
[Commercial meshers] Trimmed cell and embedded refinement mesh conversion issues | michele | OpenFOAM Meshing & Mesh Conversion | 2 | July 15, 2005 05:15 |