-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
Allowing FVDrichletBCs to take state #29145
Labels
Comments
tanoret
added a commit
to tanoret/moose
that referenced
this issue
Nov 26, 2024
tanoret
added a commit
to tanoret/moose
that referenced
this issue
Nov 26, 2024
tanoret
added a commit
to tanoret/moose
that referenced
this issue
Nov 26, 2024
Co-authored-by: Peter German <31662443+grmnptr@users.noreply.github.com>
tanoret
added a commit
to tanoret/moose
that referenced
this issue
Nov 26, 2024
…daholab#29145 Co-authored-by: Peter German <31662443+grmnptr@users.noreply.github.com>
tanoret
added a commit
to tanoret/moose
that referenced
this issue
Nov 26, 2024
tanoret
added a commit
to tanoret/moose
that referenced
this issue
Nov 26, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Motivation
Currently Dirichlet BCs in the FV framework are hardcoded to use the current state. This is inconvenient if we want Dirichlet BCs to take a previous state of a functor.
Design
Modify the
getDirichletBoundaryFaceValue
function inMooseVariableFV
to use the state provided to this function and extend theboundaryValue
getter in Dirichlet BCs to take the state provided to this function. Also, remove the assert that ensures that state.state is 0Impact
More flexibility when using FV Dirichlet BCs or developing new derived classes from FVDirichletBCs
The text was updated successfully, but these errors were encountered: