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
Empty neighbor lists from FancyExtruderGenerator
#15936
Labels
C: Meshing
MeshGenerator system, mesh loading
P: normal
A defect affecting operation with a low possibility of significantly affects.
T: defect
An anomaly, which is anything that deviates from expectations.
Comments
smharper
added
the
T: defect
An anomaly, which is anything that deviates from expectations.
label
Oct 13, 2020
smharper
added a commit
to smharper/moose
that referenced
this issue
Oct 13, 2020
This was referenced 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
aeslaughter
added
the
P: normal
A defect affecting operation with a low possibility of significantly affects.
label
Apr 12, 2021
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: Meshing
MeshGenerator system, mesh loading
P: normal
A defect affecting operation with a low possibility of significantly affects.
T: defect
An anomaly, which is anything that deviates from expectations.
The mesh output by the
FancyExtruderGenerator
does not have the neighbors specified for each element. In other words,elem->neighbor_ptr
returnsnullptr
for each side of the new elements.This information is needed for the sideset generators like
SideSetsBetweenSubdomainsGenerator
so currently those generators will not work when their input is created byFancyExtruderGenerator
.This needs to be fixed by calling
find_neighbors
(orprepare_for_use
which in turn callsfind_neighbors
) somewhere along the mesh generation train.The text was updated successfully, but these errors were encountered: