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
[9.5] Refactor grid fixup functions #13820
[9.5] Refactor grid fixup functions #13820
Conversation
On second thought, this might break things in a weird way (it at least substantially changes the behavior of loading mixed meshes) so lets hold off until 9.5. If necessary users can always fix meshes themselves. |
4a1136b
to
314d713
Compare
One test fails:
|
Hm. We might want to keep throwing that exception - it is a lot more informative than an internal error. I'll see if I can get that to work. |
@drwells Any news? |
Not yet. I've been traveling for most of the last two weeks and I haven't had time to look at this. |
314d713
to
4f6085d
Compare
That was pretty easy to address - all we need to do is switch to the correct exception type here. |
4f6085d
to
74b3469
Compare
/rebuild |
74b3469
to
937a516
Compare
Can someone take another look? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nice!
We can do better than an internal error in the GridTools function.
This exposes a few issues with the ExodusII test grids.
937a516
to
f654ef0
Compare
Followup to #13765 and #13766.
We typically (but not always) call the same three grid fixup functions after loading in data. This PR adds a utility function for calling all of them in the right order under the correct circumstances. As of #13766 we can detect twisted pyramids and wedges, so we can call
GridTools::invert_cells_with_negative_measure()
for all types of supported meshes.