You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In CFD it could be advantageous to have elements be on a different subdomain right next to the boundary so we can apply wall treatments using block restriction
I was trying to use it to get a functor to be defined on the same subdomain as another functor to define a functor material that uses both on the boundary
Design
Add an included_boundaries parameter to the ParsedSubdomainGenerator
Add some logic to exclude elements that do not lie on the included boundaries
Impact
More flexibility and capability while meshing
The text was updated successfully, but these errors were encountered:
Motivation
In CFD it could be advantageous to have elements be on a different subdomain right next to the boundary so we can apply wall treatments using block restriction
I was trying to use it to get a functor to be defined on the same subdomain as another functor to define a functor material that uses both on the boundary
Design
Add an included_boundaries parameter to the ParsedSubdomainGenerator
Add some logic to exclude elements that do not lie on the included boundaries
Impact
More flexibility and capability while meshing
The text was updated successfully, but these errors were encountered: