RenameBoundaryGenerator does not handle merging boundaries #15786
Labels
C: Framework
C: Meshing
MeshGenerator system, mesh loading
Good first issue
P: normal
A defect affecting operation with a low possibility of significantly affects.
T: task
An enhancement to the software.
Reason
From Joe Kelley at the NRC:
I am working on a 7-cell model that uses the GapHeatTransfer BC for every pair of sidesets as was done for the "reference" calculation in the extended scope task.
In that calculation, there were only two axial regions in the meshing-tools script, the support plate and everything else. Unfortunately, the real geometry has 6 axial regions above the support plate (eg, lower reflector, fuel, etc). I don't want to have to specify GapHeatTransfer BCs for every axial level (if possible) as that would result in 6x12 = 72 BCs. I'd much rather just have to deal with only 12 BCs (especially as the tensor mechanics part is going to have to change the gap width for all of these).
So, why not merge them into one boundary (sideset) for all the axial regions of a given face? This is what I tried putting in a Mesh block:
This does indeed collapse all 6 axial levels into one sideset. But, the axial extent of that sideset is only the first level.
Design
Being able to merge sidesets when renaming seems like a logical feature that should be supported. If not, we probably should produce a concise error explaining why we can't do this instead of giving the incorrect result.
Impact
Minor annoyance - but should be improved for better useability
The text was updated successfully, but these errors were encountered: