Fix aachen testcase by alecappiello · Pull Request #2367 · su2code/SU2

Proposed Changes

I discovered that the Aachen regression test was actually on its way to divergence. I think this explains why the regression test was behaving inconsistently, although I'm not sure about what caused this problem.

I made a new mesh, introduced wall functions as suggested by @joshkellyjak, and switched to second order directly.
The convergence history is good. See the attached convergence histories obtained with JST starting from scratch with outlet pressure ramp.
conv_hist_rotor1
conv_hist_stator1
conv_hist_stator2

I have finally updated the restart files accordingly.

Related Work

I think these small changes could fix the issues encountered in the past with this test case.

PR Checklist

Put an X by all that apply. You can fill this out after submitting the PR. If you have any questions, don't hesitate to ask! We want to help. These are a guide for you to know what the reviewers will be looking for in your contribution.

  • I am submitting my contribution to the develop branch.
  • My contribution generates no new compiler warnings (try with --warnlevel=3 when using meson).
  • My contribution is commented and consistent with SU2 style (https://su2code.github.io/docs_v7/Style-Guide/).
  • I used the pre-commit hook to prevent dirty commits and used pre-commit run --all to format old commits.
  • I have added a test case that demonstrates my contribution, if necessary.
  • I have updated appropriate documentation (Tutorials, Docs Page, config_template.cpp), if necessary.