-
Notifications
You must be signed in to change notification settings - Fork 285
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
XYDG Meshing Around a Single Disjointed Mesh #3578
Comments
Tagging @miaoyinb for his comments here on what could potentially be addressed by the upcoming FlexiblePatternGenerator |
I ran across #1902 again today, and I'm wondering if I can kill two birds with one stone here. A flood algorithm that fills an unordered_set (or maybe an id-indexed set; don't want to get burned in parallel again...) of elements would be useful for both identifying disconnected meshes and making copies of connected components for use in But now here's something that scares me a bit: are we likely to come up with cases where a mesh itself is connected but its interior is not? E.g. two quads like:
No flood-fill based on neighbor (and for adapted meshes, parent) links will find a connection that only goes through one vertex. We've got other code in libMesh (at least in distributed-memory-mesh repartitioning code paths, possibly elsewhere) that already does not handle this case well, IIRC. |
I am working on this new |
|
FEATURE REQUEST
Issue
Currently,
XYDelaunayGenerator
(XYDG) cannot mesh the area around a single mesh with disjointed pieces. The use case for this is designing an assembly usingHexIDPatternedMeshGenerator
and then deleting the background of the created assembly, preserving only the pins, and then drawing a hexagon and maybe some circles inside the assembly for wires or control drums. XYDG works if each pin is defined as it own mesh, but if all the pins come from an assembly mesh with its background deleted, this does not work.Feature
Ability to pass a single mesh consisting of disconnected parts and XYDG will mesh around those disconnected parts.
Work Around
Currently I can workaround this for single control rods by creating my hexagonal pin cell mesh, and then ONLY deleting pin cells where I want to put my control drum, thereby creating a hole in the hexagonal assembly, and then putting the control drum in this hole and meshing around that.
The problem with this approach is that the control drum CANNOT intersect with the pin cells (pin + background in cell). This could be a problem as physically there is no reason a control drum or control rod channel could not intersect with the pin background of a cell. This cannot be meshed currently unless doing the aforementioned explicitly meshing individual pins.
Tag @roystgnr @eshemon
The text was updated successfully, but these errors were encountered: