Not preparing for use before exodus output can leave the mesh incompatible with Paraview #27668
Labels
C: Meshing
MeshGenerator system, mesh loading
P: minor
A defect that does not affect the accuracy of results.
T: defect
An anomaly, which is anything that deviates from expectations.
Bug Description
I was modifying the AdvancedExtruderGenerator to handle Quad8 and it left a lot of issues in the boundary_info that could have been handled by a prepare_for_use before outputting the mesh
the problem is that in the process of mesh generator, more nodes are added to the mesh and the boundary_info than necessary.
I could see element deletion generators facing the same issues. If we delete elements but leave their nodes in the boundary info
note that this would be an issue also for intermediate post-each mesh generator outputs
Paraview crashes on having nodes in nodesets that are not present in the mesh
Exodiff reports cryptic diffs with seemingly some OOB indexes
Steps to Reproduce
Use the AdvancedExtruded with QUAD8, dont prepare for use
Impact
Not much now that we are aware of the problem
Preparing for use could be potentially expensive which is why we dont do it
[Optional] Diagnostics
No response
The text was updated successfully, but these errors were encountered: