|
[Sponsors] |
November 19, 2008, 08:22 |
sliding meshes
|
#1 |
Guest
Posts: n/a
|
Hello. I am attempting to simulate the rotation of a water turbine using sliding meshes. The fluent manual states that if 2 zones are meshed independently, it is necessary to merge them. Does this mean that for all sliding mesh problems it is necessary to use t-merge, or can this be done without the use of t-merge.
Also when 2 interfaces assigned in gambit are combined to make a single grid interface, walls are created as boundary zones. Does the fact that these are specified as walls make a problem, and what boundary condition type should they be changed to if so? Thanks. |
|
November 19, 2008, 16:27 |
Re: sliding meshes
|
#2 |
Guest
Posts: n/a
|
try to use Tgrid instead which is more convinient that tfiler tmerge
|
|
November 19, 2008, 16:32 |
Re: sliding meshes
|
#3 |
Guest
Posts: n/a
|
import two meshe files in Tgrid and save them as one mesh file can be read in fluent
|
|
November 20, 2008, 09:20 |
Re: sliding meshes
|
#4 |
Guest
Posts: n/a
|
Hi Tim
Regarding your gambit query ------Even if you define walls in gambit to interface zones you can change it to interface b.c. in Fluent. For naming conventions you can use Rotor:intf1/Casing:intf1 as in your case for turbine. which would be easier for you to find the couple on interfaces defination panel in fluent And do remember to change the b.c. of these intf# to interface b.c. from boundary condition panel... Hope so i have understood your query and answered ..... if its different we can discuss.....to resolve it...... Uday |
|
|
|
Similar Threads | ||||
Thread | Thread Starter | Forum | Replies | Last Post |
sliding meshes | GU | FLUENT | 0 | May 9, 2006 07:50 |
Sliding meshes | Vijay | FLUENT | 0 | December 16, 2005 01:47 |
Sliding meshes and meshing | Joel | Siemens | 0 | September 9, 2002 07:35 |
Arbitrary Sliding Meshes | Anna | Siemens | 0 | September 1, 2002 07:02 |
Sliding meshes-compressible. | Pierre Ricco | FLUENT | 1 | March 8, 2001 07:10 |