I am trying to learn more about reading results out after running a simulation. I have done a couple of 2D simulations with a thin plate at 5 deg angle of attack, with a freestream velocity of 100 ft/s. I chose this because I wanted something simple that I could check with hand calculations, but I am running into some differences that seem fairly substantial to me.

Theoretically, the lift coefficient for a thin, flat plate at low angles of attack should be 2*π*alpha (rad). This says that the lift coefficient for a flat plate at 5 deg should be about 0.548. Lift is given as (0.5*ρ*v²)*S*Cl, where rho is air density, v is freestream velocity, S is the wing or airfoil area, and Cl is the lift coefficient.

When doing a 2D simulation, the thickness of the simulation was automatically set to what is equal to 0.2 inches giving the plate an area of 0.01667 ft^2 yielding a theoretical lift of 0.109 lbs, or exactly 1/5 of the lift of the entire plate. This does not match my findings for either case. Please see attachments for my setup and results.

The table below shows the collected data

Theoretical CL | 0.548311 | ||

Lift (lb) | |||

fluid region | Area (ft^{2}) | Theoretic | Simulation |

partial | 0.016667 | 0.108611 | 0.073 |

complete | 0.083333 | 0.543057 | 0.3763 |

Thank you in advance for any information on why these approximations and simulations are not in better agreement.

Josiah

Above is the computation region for both simulations

Above is the section view showing the narrower section 0.2 inches across

Above is the section view showing the wider region 1 in. wide

Above is the view of the lower quality mesh. For the wider region, I was running into some computation errors that estimated 50 hours to solve, so I lowered the resolution to what is shown above.

Above are the surface forces for the narrower region

Above are the surface forces for the wider region

I haven't looked into confirming your theoretical calcs and what assumptions are made for them but I would recommend posting your references here. I would also recommend doing some research on how close those calcs come to actual tests.

regarding your flow simulation setup a few comments:

1. what is partial vs complete? i'm not sure I understand

2. when doing 2D simulation, you want the thickness to be as thin as possible. even if the default is 0.2inches, I would go even smaller than that. the solver is still solving a full 3d problem, just with one cell thickness, so you want to minimize the chance of any flow out of the 2d plane from having to be calculated. in general I try to keep it's width so that it correlates with the smallest element size so that I have as close to cubic cells as possible.

3. with respect to your comparison, make sure that your theoretical calcs aren't including any edge/end effects since 2d simulation is assuming it is infinitely long. I would also recommend working with lift force/length so that you're not converting the 2d thickness to 3d.

4. for your mesh, and your comp domain, I would say the size of the cells is still too big and your comp domain is too small. but without a plot of what the flow looks like it is hard to say on the comp domain. for the cell size, it may take 50hrs, but you're going to have to do a mesh convergence check to know if you have an appropriate element size. and you're going to also have to consider convergence criteria and the convergence graphs.

5. I also believe the developers recommend turning the flow rather than turning the components. check the soliworks kb on this.

6. regarding plotting, i'm assuming you are choosing all faces when plotting. if not, you will get incorrect results. I would also recommend creating global and surface goals to make export easy.

overall, this is a really good thing to do before you move onto more complicated problems. it really shows how big the comp domain needs to be, how many cells you need and what level of complexity is reasonable for cfd and whether it is practical or not. there is a good article about this in the kb as well.

I would also recommend you take a look at the validation example of a flow over a sphere. it will comment on all the things I have mentioned here in addition to whether a steady state solution is correct or not. also, it should give you more confidence that the issue you are running into is not necessarily that flow is solving the problem incorrectly but rather it is just a bump in the road from gaining experience in using the software. at hawk ridge we spend a lot of time with customers working through these bumps with our mentoring service.