Enhance FileMeshGenerator so that it can use elemental variables in Exodus to set element integers #14916
Labels
C: Framework
P: normal
A defect affecting operation with a low possibility of significantly affects.
T: task
An enhancement to the software.
Comments
YaqiWang
added
P: normal
YaqiWang
added a commit
to YaqiWang/moose
that referenced
this issue
Mar 18, 2020
YaqiWang
added a commit
to YaqiWang/moose
that referenced
this issue
Mar 19, 2020
YaqiWang
added a commit
to YaqiWang/moose
that referenced
this issue
Apr 6, 2020
YaqiWang
added a commit
to YaqiWang/moose
that referenced
this issue
Apr 6, 2020
YaqiWang
added a commit
to YaqiWang/moose
that referenced
this issue
Apr 6, 2020
killerpenguin12
pushed a commit
to killerpenguin12/moose
that referenced
this issue
Apr 13, 2020
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Reason
Element integers are extremely useful for reactor analysis where lots of materials could be potentially used. We had something called
FileIDMeshin our application in the past before extra integer ids are formally supported by libMesh. That code mostly works well except the difficulties with restart and recover. We need to refactor that code to use our new mesh generator system with the newly supported extra element integers.Design
After changes I made in libMesh/libmesh#2471, we simply need to change the
FileMeshGeneratora little to support this.Impact
New capability.
The text was updated successfully, but these errors were encountered: