Author: Julio Sampaio Gabriel de Pieri, Cornell University
Problem Specification
1. Pre-Analysis & Start-Up
2. Geometry
3. Mesh
4. Physics Setup
5. Numerical Solution
6. Numerical Results
7. Verification & Validation
Exercises
Comments
Physics Setup
Outline
-Launch fluent by double clicking the Solution Cell on the new Sliding mesh project (select double precision. This is gonna be a heavy simulation, so it is a good idea to select parallel. But note that overhead in parallel actually slows down the simulation, as the communication between the cores starts to become slow compared to the time they take to calculate. For here simulation 2-3 cores are enough.)
-(the warning message "zone-surface annonc create surface from sliding interface" appears when Fluent reads the case and data files. It means that the boundaries of the non-conformal interfaces match exactly (i.e., there is no overlapping section on either side of the interface)).
-Check BCs etc (some setup values were imported to Fluent already. Let's confirm that. (check BC, model, plot a velocity contour to see if the results coming from the MRF file are ok))
-General: Transient (As our model will move, we are solving a transient model).
-Cell zone conditions (here is where we specify that we want the sliding mesh. Remember that we selected "Frame Motion"? Now we will copy that info into the Mesh Motion option)
-- For "inner", click edit and then click copy to mesh motion. Go into the tab and check that the rotation speed (relative to correct zone) and has been transferred.
-- For each fluid-blade zone, "Copy to Mesh Motion". Move to mesh motion tab and check that the origin and angular velocity were transferred.
--For all three blades, the motion should be relative to the "inner" zone. Therefore each blade will not only rotate about its own axis, but also its axis will translate to follow the motion of the hub (called "inner" here).
If you get an error saying that no interface zones were created, launch fluent from Setup in MFR, re-assign the interfaces and run the simulation again.
Under Construction