-
Notifications
You must be signed in to change notification settings - Fork 843
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
[WIP] Fix NEMO Inlet BC #1882
base: develop
Are you sure you want to change the base?
[WIP] Fix NEMO Inlet BC #1882
Conversation
Signed-off-by: jtneedels <[email protected]>
Need to figure out how to adapt for noneq flows. I haven't been able to find a separate description of how to solve for boundary conditions for noneq flows with Riemann invariants. |
Signed-off-by: jtneedels <[email protected]>
I've thought about this a bit, and I think the best way forward for this BC is to assume thermal equilibirum in the subsonic flow. In that case the ongoing characteristic for total density can be used to solve for the full thermodynamic state. I think this probably is consistent with use cases such as fuel injection in scramjets, where the injected fluid would be in thermodynamic equilibrium. |
Signed-off-by: jtneedels <[email protected]>
Signed-off-by: jtneedels <[email protected]>
Signed-off-by: jtneedels <[email protected]>
Signed-off-by: jtneedels <[email protected]>
…nto feature_nemo_inlet
@pcarruscag PTAL what would be the best way to handle variable declarations with the switch statement? Either they all need to be pre-declared at the top of the function, or I can declare them inline and restrict the scope, but then the residual computation needs to take place in each case. Which of these ways would be preferred? |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. If this is still a relevant issue please comment on it to restart the discussion. Thank you for your contributions. |
Proposed Changes
Fix NEMO inlet BC.
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.