-
Notifications
You must be signed in to change notification settings - Fork 902
[WIP] Automating First Order Initialisation When Using MUSCL #2544
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
base: develop
Are you sure you want to change the base?
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nice work! Would love to see this extended to multizone it would be super useful for turbo optimisation. In this regard maybe it is easier to refactor to run via a call to StartSolver from the higher level driver?
| * \return yes/no. | ||
| */ | ||
| bool GetFirst_Order_Init(void) const { return First_Order_Initialization; } | ||
| void SetFirst_Order_Init(bool val_update) { First_Order_Initialization = val_update; } |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Add similar documentation
| /*! | ||
| * \brief Perform a first order simulation as an initial solution before running MUSCL reconstructed flow. | ||
| */ | ||
| void FirstOrderInit(); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can this be expanded to multizone?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hi Josh, I'm planning on refactoring the logic to the Iteration class then call it in the Solver. Once its running I'll work on the MZ solver.
I also want to look into the idea Tom and Juan mentioned at the conference about progressively ramping up the MUSCL reconstruction which I think can be done by gradually scaling the gradient limiters over some iterations.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Sounds good.
For the gradual ramping we have a ramp feature in the turbomachinery world you may find useful for this.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
See #2581
Proposed Changes
Give a brief overview of your contribution here in a few sentences.
A first order simulation is commonly used as an initial solution when performing a second order (MUSCL) reconstructed simulation. This PR aims to automate this process rather than having to do it manually, saving some time.
Related Work
Resolve any issues (bug fix or feature request), note any related PRs, or mention interactions with the work of others, if any.
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.
pre-commit run --allto format old commits.