Open lindsayad opened 5 years ago
I would like to be involved with this, I have an interest in doing this for simulating snow accumulation.
I am interested in this too. When couple bison and rattlesnake for modeling fuel rods, bison does not mesh the gap but rattlesnake needs to. In order to let rattlesnake use the displaced mesh from bison, we need this to handle the gap closure rigorously. I know Triangle for 2D or TetGen for 3D could be another option. Either one, we can have a mesher first in the new mesh generation system and then add the on-the-fly mesh generation and re-distribution capability.
I would like to contribute to this. I got a mass growth problem at the boundary, which needs remesh to the model with newly generated mass. I don't have experience in developing MOOSE, but wrote my own ALE and remeshing code before.
Reason
A couple possible reasons:
Design
libMesh will have to do the heavy lifting for this. This is kind of a blue sky feature request so I don't have a hard design in mind at this point. Whenever we have discussions about this it seems like we stop after discussing parallel mesh generation. An initial cut might serialize the mesh, re-mesh, and then re-distribute.
We'll need to do mesh generation on the fly. The new C++ API in gmsh may be a huge boon for this.
Impact
More flexible large deformation, ALE, and mesh generation simulations.