Skip to content
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

Sideset generators need neighbors #15823

Open
loganharbour opened this issue Sep 17, 2020 · 0 comments
Open

Sideset generators need neighbors #15823

loganharbour opened this issue Sep 17, 2020 · 0 comments
Labels
C: Framework P: normal A defect affecting operation with a low possibility of significantly affects. T: task An enhancement to the software.

Comments

@loganharbour
Copy link
Member

loganharbour commented Sep 17, 2020

Reason

We check elem->neighbor_ptr(side) in SideSetsGeneratorBase to exclude element sides that aren't on the boundary. Depending on the status of the input mesh, the neighbors may not be built.

Issue found by @gridley.

Design

Call find_neighbors() on the mesh up front in SideSetsGeneratorBase. Or, come up with a way to set a flag in generators for if the neighbors are needed or not. This issue could easily extend past just SideSetsGeneratorBase.

Impact

Will make SideSetsGeneratorBase produce the intended behavior for only adding sidesets to boundary sides.

@loganharbour loganharbour added C: Framework T: task An enhancement to the software. P: normal A defect affecting operation with a low possibility of significantly affects. labels Sep 17, 2020
loganharbour added a commit to loganharbour/moose that referenced this issue Sep 17, 2020
loganharbour added a commit to loganharbour/moose that referenced this issue Sep 17, 2020
loganharbour added a commit to loganharbour/moose that referenced this issue Sep 27, 2020
loganharbour added a commit to loganharbour/moose that referenced this issue Sep 27, 2020
loganharbour added a commit to loganharbour/moose that referenced this issue Sep 27, 2020
@loganharbour loganharbour changed the title Sideset generators need normals Sideset generators need neighbors Oct 13, 2020
lindsayad added a commit to lindsayad/moose that referenced this issue Oct 27, 2020
We also can signal to the `MeshBase` object if we've done some
operation that renders the mesh unprepared. If we do this meticulously
then we can trust checks of the `is_prepared` flag to tell us when we
need to `prepare_for_use` or not

Closes idaholab#15944 idaholab#15936 idaholab#15823
lindsayad added a commit to lindsayad/moose that referenced this issue Oct 27, 2020
We also can signal to the `MeshBase` object if we've done some
operation that renders the mesh unprepared. If we do this meticulously
then we can trust checks of the `is_prepared` flag to tell us when we
need to `prepare_for_use` or not

Closes idaholab#15944 idaholab#15936 idaholab#15823
lindsayad added a commit to lindsayad/moose that referenced this issue Oct 27, 2020
We also can signal to the `MeshBase` object if we've done some
operation that renders the mesh unprepared. If we do this meticulously
then we can trust checks of the `is_prepared` flag to tell us when we
need to `prepare_for_use` or not

Closes idaholab#15944 idaholab#15936 idaholab#15823
smharper pushed a commit to smharper/moose that referenced this issue Nov 11, 2020
We also can signal to the `MeshBase` object if we've done some
operation that renders the mesh unprepared. If we do this meticulously
then we can trust checks of the `is_prepared` flag to tell us when we
need to `prepare_for_use` or not

Closes idaholab#15944 idaholab#15936 idaholab#15823
smharper pushed a commit to smharper/moose that referenced this issue Nov 11, 2020
We also can signal to the `MeshBase` object if we've done some
operation that renders the mesh unprepared. If we do this meticulously
then we can trust checks of the `is_prepared` flag to tell us when we
need to `prepare_for_use` or not

Closes idaholab#15944 idaholab#15936 idaholab#15823
lindsayad added a commit to lindsayad/moose that referenced this issue Nov 11, 2020
We also can signal to the `MeshBase` object if we've done some
operation that renders the mesh unprepared. If we do this meticulously
then we can trust checks of the `is_prepared` flag to tell us when we
need to `prepare_for_use` or not

Closes idaholab#15944 idaholab#15936 idaholab#15823
lindsayad added a commit to lindsayad/moose that referenced this issue Nov 11, 2020
We also can signal to the `MeshBase` object if we've done some
operation that renders the mesh unprepared. If we do this meticulously
then we can trust checks of the `is_prepared` flag to tell us when we
need to `prepare_for_use` or not

Closes idaholab#15944 idaholab#15936 idaholab#15823
lindsayad added a commit to lindsayad/moose that referenced this issue Dec 18, 2020
We also can signal to the `MeshBase` object if we've done some
operation that renders the mesh unprepared. If we do this meticulously
then we can trust checks of the `is_prepared` flag to tell us when we
need to `prepare_for_use` or not

Closes idaholab#15944 idaholab#15936 idaholab#15823
lindsayad added a commit to lindsayad/moose that referenced this issue Dec 18, 2020
We also can signal to the `MeshBase` object if we've done some
operation that renders the mesh unprepared. If we do this meticulously
then we can trust checks of the `is_prepared` flag to tell us when we
need to `prepare_for_use` or not

Closes idaholab#15944 idaholab#15936 idaholab#15823
lindsayad added a commit to lindsayad/moose that referenced this issue Dec 18, 2020
We also can signal to the `MeshBase` object if we've done some
operation that renders the mesh unprepared. If we do this meticulously
then we can trust checks of the `is_prepared` flag to tell us when we
need to `prepare_for_use` or not

Closes idaholab#15944 idaholab#15936 idaholab#15823
lindsayad added a commit to lindsayad/moose that referenced this issue Dec 28, 2020
We also can signal to the `MeshBase` object if we've done some
operation that renders the mesh unprepared. If we do this meticulously
then we can trust checks of the `is_prepared` flag to tell us when we
need to `prepare_for_use` or not

Closes idaholab#15944 idaholab#15936 idaholab#15823
lindsayad added a commit to lindsayad/moose that referenced this issue Jan 4, 2021
We also can signal to the `MeshBase` object if we've done some
operation that renders the mesh unprepared. If we do this meticulously
then we can trust checks of the `is_prepared` flag to tell us when we
need to `prepare_for_use` or not

Closes idaholab#15944 idaholab#15936 idaholab#15823
jain651 pushed a commit to jain651/moose that referenced this issue Apr 19, 2021
We also can signal to the `MeshBase` object if we've done some
operation that renders the mesh unprepared. If we do this meticulously
then we can trust checks of the `is_prepared` flag to tell us when we
need to `prepare_for_use` or not

Closes idaholab#15944 idaholab#15936 idaholab#15823
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
C: Framework P: normal A defect affecting operation with a low possibility of significantly affects. T: task An enhancement to the software.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant