Skip to content
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

Update .cfg files to comply with SU2 v 7.2.1 #3

Open
wants to merge 3 commits into
base: master
Choose a base branch
from

Conversation

clmurphey
Copy link

Proposed Changes

Related Work

  • Initial Commits on master branch

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 updates.

  • My contribution generates no new compiler warnings (try with the '-Wall -Wextra -Wno-unused-parameter -Wno-empty-body' compiler flags, or simply --warnlevel=2 when using meson).
  • My contribution is commented and consistent with SU2 style.
  • 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.

- Update `.cfg` files within the `mms` directory to comply with the latest config_template.cfg in https://github.com/su2code/SU2/blob/5655d91d7da192ad0b2a231f9ab5334c2235c10a/config_template.cfg
- Update instances each copy of `compute_order_accuracy.py` to comply with Python 3.9 syntax (e.g., print statements)
I have added `time_convergence.py`, a Python script based on `computer_order_of_accuracy.py` [here](https://github.com/su2code/VandV/blob/ad27cdf9391c9077f3ef14949e29c01be428b0d9/mms/fvm_navierstokes/compute_order_of_accuracy.py). This script loops over various different time marching schemes (e.g., `TIME_MARCHING = TIME_STEPPING`, `TIME_MARCHING = DUAL-TIME_STEPPING-1ST_ORDER`, `TIME_MARCHING = DUAL-TIME_STEPPING-2ND_ORDER`) for each of SU2's Navier Stokes Solvers (e.g., `FEM_NAVIER_STOKES` and `NAVIER_STOKES`) using different numerical methods (e.g., DG, JST, ROE+LIM, ROE, ROW+WLS).  Each case is evaluated at a different `TIME_STEP` size [1e-6 : 1e-10].
commented out a few plots and rearranged the directory.
Copy link
Member

@pcarruscag pcarruscag left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Wow thank you for the updates @clmurphey, I did not get all notification on this repository, sorry for the delay.
Few questions:

  • Can you present this work at one of the developer meetings? Wednesdays at 3pm UK, https://meet.jit.si/SU2_DevMeeting
  • I suppose a lot of the new files are created automatically? i.e. the meshes are generated and the .vtu files etc. are produced by SU2, and the new images from python?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants