su2code / SU2

SU2: An Open-Source Suite for Multiphysics Simulation and Design
https://su2code.github.io
Other
1.33k stars 841 forks source link

RANS simulations on 3D wing - convergence problem #533

Closed acrovato closed 4 years ago

acrovato commented 6 years ago

Dear SU2 developers and users,

I am running RANS simulations around a typical aircraft wing (EBW in the following) and I am facing some issues.

Here are the flight conditions:

At these conditions, the EBW should produce a lift coefficient between [0.4;0.5]. However, when SU2 converges, the Cl is about 0.27 and the Cd is negative.

Here follows a summary of what I have done.

I have used several (multiblock structured) meshes:

At the preprocessing stage when computing the projection area of the EBW in the z-plane, I noticed that the meshes generated by Gmsh gave a wrong projection (~30 m2 instead of ~40 m2!). I increased the height of the first cell in the boundary layer (which was set to match y+ ~ 1) and the problem disappeared when y+ got close to 30. Of course, this mesh is not usable without wall functions... However, it does not seem to be the only problem since:

I also tried to tune these different numerical parameters, without success:

To make sure that SU2 was correctly compiled, I also:

Finally, I also ran the case with the Euler equations, on the EBW meshed with Gmsh, and recovered the expected results.

In summary, I have tried several meshes from different software, with different numerical parameters on different SU2 versions, but always got bad results when solving RANS equations. Particularly, the Gmsh mesh preprocessing on SU2 gave a bad z-projection of the EBW. However, the same meshes gave converged results on CFD++.

Any help or ideas would be appreciated. Many thanks in advance.

vdweide commented 6 years ago

Would it be possible to make available the Gmsh mesh and the config file?

hlkline commented 6 years ago

I noticed you mentioned that it is a multiblock structured mesh. SU2 expects a single block format, unless explicitly setting up a multi zone problem, so there's an outside chance it's only loading part of the mesh. I would expect that to throw some kind of error, but it's worth checking. This could explain the wrong z projection, but to check you can plot the output volume solution to see if your mesh is loaded appropriately.

acrovato commented 6 years ago

@vdweide: I cannot give you the geometry or the mesh because they are the property of an aircraft manufacturer, a colleague is going to check if he can provide a dummy geometry, similar to the one we are working onto. What I can give you is the config file (I still had to change some values related to the geometry).

@hlkline: What I meant was that the meshes were generated using a multi block strategy. Before writing into SU2 or CGNS, they were converted in a proper unstructured format. I had indeed checked the surface solution, but not the volume one. And it seems that there are some weird cells (see attached screenshot). I will investigate.

Thanks for your inputs!

EBW2v2.txt

volume

vdweide commented 6 years ago

The config file is a start, but for a thorough investigation a full test case, i.e. including a grid, is preferable.

acrovato commented 6 years ago

Hi there,

I went ahead and created a dummy geometry, that is:

  1. I altered the planform so that the sweep, twist, dihedral, taper... are now different from the actual wing
  2. I replaced the airfoil by the NASA SC(2)-0712

The dummy wing has a double planform defined as:

I defined the reference length as:

The flight conditions remained unchanged:

I created the exact same grid as before (same number of cells, same progression), ensuring my first cell was at y+<1.

Things is, this time, SU2 did not have any trouble converging and computed the right z-projected area... I checked the results with another software and the pressure distribution (taken along the chord near the kink) match, see attached Figure.

I am attaching the dummy configuration file (dum.txt) as well as the mesh (dum_mesh.txt) if it can be of interest to you. The mesh is a .geo gmsh file. To get the mesh, simply open with gmsh and click mesh 3D (or, from the console: gmsh dum_mesh.txt -3).

At this point, I think that my problem might be related to the actual wing airfoil geometry, which is somehow not well pre-processed by SU2... I will continue investigating and keep you posted if I find a solution.

Thank you for the time you took reading this issue. cp dum.txt dum_mesh.txt

acrovato commented 6 years ago

Dear SU2 users,

I continued the investigation and managed to track down the source of the problem. The issues I face with SU2 appear when my wing geometry has several airfoils across the span.

I ran several cases with supercritical airfoils and NACA 4 digits airfoils. As soon as the airfoil was changing along the span, SU2 had troubles computing the projected and wetted area of the wing, an attaining a correct solution.

To better illustrate the issue, I attached a SU2 .cfg file (dummy.txt) and Gmsh .geo file (dummy_mesh.txt) to this post. The geometry is the same as in the previous post except that I used 3 different airfoils along the span. That is, I replaced the NASA SC(2)-0712 by the {NASA SC(2)-0714, NASA SC(2)-0712, NASA SC(3)-0712}. These airfoils are similar, so I expected to recover similar results. However, I observed that:

I am unsure if the problem appears because Gmsh has trouble in generating this kind of mesh or because SU2 has trouble reading it.

Any ideas are welcome.

Thank you again, Adrien

cp y dummy_mesh.txt dummy.txt log.txt

stale[bot] commented 4 years ago

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. If this is still a relevant issue please comment on it to restart the discussion. Thank you for your contributions.