Fix aachen testcase

[alecappiello]

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.

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.

• [X] I am submitting my contribution to the develop branch.
• [X] My contribution generates no new compiler warnings (try with --warnlevel=3 when using meson).
• [X] 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.

[joshkellyjak]

@pcarruscag I think we may have spoken about this before but my memory does not serve me well, do you have any idea as to why the residual values change when we remove the entropy fix coeff?

[pcarruscag]

hmm maybe boundaries, we still use the Roe scheme on boundaries even with JST, I stand corrected.