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

Better error message when Sideset or Nodeset cannot be found #13509

Closed
permcody opened this issue Jun 3, 2019 · 0 comments
Closed

Better error message when Sideset or Nodeset cannot be found #13509

permcody opened this issue Jun 3, 2019 · 0 comments
Labels
C: Modules Good first issue 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

@permcody
Copy link
Member

permcody commented Jun 3, 2019

Bug Description

MOOSE gives an error message saying that certain "boundaries" do not exist in the mesh when in fact they do. The problem is that sometimes a specific type of boundary is missing (e.g. often a sideset doesn't exist but there's a nodeset with the given boundary ID). The error message is misleading and leaves the user confused as to what the problem is.

Steps to Reproduce

This error has arisen in several instances with Abaqus meshes:
https://groups.google.com/forum/?utm_medium=email&utm_source=footer#!msg/moose-users/kHlDjyzWa70/6JdRaUaXBwAJ

We should be able to create an Exodus mesh though that exhibits the same behavior by creating only a nodeset instead of a sideset that we attempt to use with an integrated boundary condition.

Impact

Minor: Generally this is isolated to bad mesh generation.

@permcody permcody added T: defect An anomaly, which is anything that deviates from expectations. C: Modules Good first issue P: normal A defect affecting operation with a low possibility of significantly affects. labels Jun 3, 2019
permcody added a commit to permcody/moose that referenced this issue Jun 17, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
C: Modules Good first issue P: normal A defect affecting operation with a low possibility of significantly affects. T: defect An anomaly, which is anything that deviates from expectations.
Projects
None yet
Development

No branches or pull requests

1 participant