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
Enable Geometry User Objects for blocks #24645
Labels
T: task
An enhancement to the software.
Comments
Actually lower-D subdomains are automatically refined and snapped along with their corresponding sidesets... |
dschwen
added a commit
to dschwen/moose
that referenced
this issue
Jun 9, 2023
It would be good to generalize this:
|
dschwen
added a commit
to dschwen/moose
that referenced
this issue
Jun 12, 2023
dschwen
added a commit
to dschwen/moose
that referenced
this issue
Jun 15, 2023
dschwen
added a commit
to dschwen/moose
that referenced
this issue
Jun 15, 2023
dschwen
added a commit
to dschwen/moose
that referenced
this issue
Jun 19, 2023
dschwen
added a commit
to dschwen/moose
that referenced
this issue
Jun 19, 2023
dschwen
added a commit
to dschwen/moose
that referenced
this issue
Jun 20, 2023
dschwen
added a commit
to dschwen/moose
that referenced
this issue
Jun 20, 2023
dschwen
added a commit
to dschwen/moose
that referenced
this issue
Jun 20, 2023
dschwen
added a commit
to dschwen/moose
that referenced
this issue
Jun 21, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Reason
When refining lower dimensional subdomains, such as secondary surface meshes for mortar contact, it would be convenient to apply a Geometry User Object to the lower D block rather than a sideset.
Geometry User Objects will "snap" a selected set of nodes to a user defined geometry. For example
GeometrySphere
can be used to place new nodes added by mesh refinement to the surface of a perfect sphere/circle.Design
In
GeometryBase::meshChanged()
we need to iterate over selected subdomain nodes in addition to boundary nodes.Impact
Added capability
The text was updated successfully, but these errors were encountered: