Issue with PeripheralTriangleMeshGenerator-defined external sideset and block naming #26541
Labels
C: Modules/Reactor
Tickets pertaining to the reactor module
P: normal
A defect affecting operation with a low possibility of significantly affects.
T: defect
An anomaly, which is anything that deviates from expectations.
Bug Description
If the PeripheralTriangleMeshGenerator is used more than once in the same mesh, it does not generate the correct external sideset and does not save the block names assigned in previous instruction block. It may be a problem with XYDelaunayGenerator, as @miaoyinb pointed out. An example of consecutive use is reported below and in the attached input file:
Steps to Reproduce
Run the attached input file with mesh-only option. If you inspect the output, you will see that the "external" sideset is not the external one.
issue_trianglemeshgenerator.txt
Impact
Users won't be able to generate the correct sideset or block assignment if PeripheralTriangleMeshGenerator is used more than once. Mitigation: You can use ParsedSideSetGenerator and RenameBlockGenerator to ensure block names and sidesets are assigned/defined correctly.
The text was updated successfully, but these errors were encountered: