-
Notifications
You must be signed in to change notification settings - Fork 85
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Convergence issue of the k-ω SST turbulence model in Nalu-Wind #1286
Comments
@BumseokLee I'm curious to learn how you are setting the BCs for inflow/outflow with C-mesh topology when you do non-zero angles of attack. |
@sayerhs I simply set the inflow/outflow BCs as below regardless of AoA. |
@BumseokLee What happens at the horizontal sections on the top and bottom at the back? Depending on angle of attack part of that will be inflow/outflow, correct? Is that being adjusted? |
@sayerhs I've also attached the turbulence eddy viscosity at AoA=15deg below. For me, it looks fine. For the 449 X 129 mesh, AoA=5 deg shows the most significant convergence stall. |
@BumseokLee It is just an inconsistency to be mindful when executing high angles of attack. This was the reason Ganesh and I had resorted to O-mesh configuration when doing the airfoil runs back in 2018-2019 timeframe. The omega oscillation is something we have seen with O-mesh as well. From what I remember, once it triggers it never really goes away in Nalu-Wind. We never got to the root cause on that one. My suspicion was the wall BC treatment. But it seems that you've already looked into it. |
@BumseokLee could you also please share the velocity vectors or streamlines for the same case as the eddy viscosity plot? I am curious to see what happens to the streamlines at those horizontal edges. |
Thanks for sharing the velocity vector plot. You will also want to check the pressure field along with the velocity field as the pressure will adjust if there is any change in the streamline direction.
OpenFOAM has an |
I've attached the pressure and velocity contours. I intentionally adjusted the range of the contour levels to see any suspicious behaviors. For example, the freestream velocity is 34.1m/s, and the contour level for the velocity contour is from 34.0 to 34.2. Some effects of the BCs are observed but they don't look suspicious for me. While I was checking the contours, I realized that the highest omega values occur at the wall. This is due to the boundary condition, which includes the division by the wall distance square. Below figure shows the omega near the trailing edge. It is seen that very high magnitudes of the omega are observed at the first few cells in the wall normal direction and at the wake average mesh. I may also need to compare this against converged cases and see how they look different. |
@BumseokLee Thanks for plotting the pressure and velocity and showing them side by side. I think that creating similar plots for all the angle of attack cases would be useful to understand the issue. Here is what I observe in your results. While benign, there is a wavy variation in pressure field, and a corresponding change in the velocity field as it nears the top horizontal section (you can see that as a faint bluish blob in the top right corner). Also it looks like pressure jumps to zero at outflow across one cell. You'll want to interrogate the points along the top boundary and the interior to be sure. I believe this is because we are enforcing a dirichlet velocity (inlet BC) at the top horizontal section and the flow is adjusting the pressure field to match this requirement as the exit velocity is not the same as the inlet velocity. I would also recommend that you restart from a converged solution and run a few timesteps and output solution at each step. That would help you visualize where in the flowfield It might also be useful to compare the solution against some of the $O-$mesh simulations you mentioned that you have available. |
Hi,
I am reporting a convergence issue with the omega transport equation of the k-ω SST turbulence model in Nalu-Wind. I’ve attached non-linear residual plots for NASA’s canonical case: the subsonic NACA0012 airfoil at Re=6e6. I used the 2-D C meshes and flow conditions from NASA Langley’s Turbulence Modeling Resource (TMR) Website. The freestream Mach number of the case in NASA TMR was 0.15 but I reduced it to 0.1.
In fact, this is not the only case that I’ve observed suspicious or inconsistent behavior in the omega transport equation. I’ve encountered similar issues (very large residuals or inconsistent convergence trend for a different number of Picard iterations) in other cases, including 2-D airfoils and 3-D blade simulations. In my tests, the sustaining terms didn’t resolve the issue.
Despite these behaviors, the residuals of the momentum (mean flow) and k still converge reasonably. Additionally, the predicted aerodynamic coefficients converge, showing good agreement with available experimental data or other numerical results. This might be due to the clipping functions of the model and/or the current implementation in Nalu-Wind.
However, the magnitude of the residuals still looks concerning. The convergence stall of the omega could slow down the overall convergence of the turbulence model and, consequently, the mean flow as well. This issue could be particularly significant in highly unsteady flow simulations, such as IDDES FSI simulations, where sufficient iterations are not available between physical time steps. It could also affect laminar-turbulent transition simulations too because the transition model triggers the transition onset within the boundary layer using the k and omega values, making it highly sensitive to near-wall values. (That’s why I previously fixed the omega boundary condition at the wall, although it doesn’t seem to make a significant difference in fully turbulent simulations.)
I haven’t yet investigated where these large residuals occur, but I believe it is worthwhile to check. I am currently occupied with some other work in my projects, so I cannot attack this issue immediately. However, I can investigate this after completing my urgent work, probably around early or mid-September. If anyone is interested in this, you are welcome. I can share the mesh and input files, or you can directly start from the NASA mesh to reproduce the issue.
The text was updated successfully, but these errors were encountered: