Skip to content

Override the fvpatch field type basedon the FoamBC class#127

Open
mattfalcone1997 wants to merge 7 commits into
aurora-multiphysics:mainfrom
mattfalcone1997:force-patch-type
Open

Override the fvpatch field type basedon the FoamBC class#127
mattfalcone1997 wants to merge 7 commits into
aurora-multiphysics:mainfrom
mattfalcone1997:force-patch-type

Conversation

@mattfalcone1997

@mattfalcone1997 mattfalcone1997 commented Jul 3, 2026

Copy link
Copy Markdown
Collaborator

Summary

Changes FoamBCBase to set the correct fvPatchField when it is initialised

Related Issue

Resolves #126

Checklist

  • Functionality implememented
    • Make sure energy BCs updated if T is updated
  • Some of the existing boundary condition tests updated to test the switch
    • laplace_fixed_gradient, fixed_value and mass_flow_rate
  • Fixed bugs in timestepper class associated with the update
  • Existing docs didn't mention need to set the correct underlying BC (as far as I can see)

@mattfalcone1997 mattfalcone1997 requested a review from k-collie July 6, 2026 13:06
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Allow Hippo to override boundary condition types specified in 0/*

1 participant