TRI7 center node adjustment and TRI6/7 degeneracy checks after midpoint relocation#4481
TRI7 center node adjustment and TRI6/7 degeneracy checks after midpoint relocation#4481miaoyinb wants to merge 2 commits into
Conversation
…midpoint relocation closes libMesh#4480
|
As this PR moves TRI7 center node, MOOSE's |
|
As a general rule "midpoint goes at the centroid" isn't always right, since you can do some clever things with boundary layers by using slightly-off-center higher order nodes in the grading, but in this context I think this is exactly the right thing to do. If you don't want to create a big "have to get the submodule updated to regold" vs "can't merge the PR without breaking a ton of recipes" chicken-and-egg problem, the general way to do that is to add new behavior as an option before we change behavior by default. Default the new behavior to "off", then after MOOSE is updated turn it on there and regold, then change the default to "on". |
|
Good point, I will make it optional. |
|
Job Distributed make check sweep (odd) on 4659afd : invalidated by @miaoyinb |
closes #4480