Skip to content
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

Adding option to automatically define block names in RGMB mesh generators from region ID #27673

Open
shikhar413 opened this issue May 20, 2024 · 0 comments
Labels
T: task An enhancement to the software.

Comments

@shikhar413
Copy link
Contributor

shikhar413 commented May 20, 2024

Motivation

The Griffin team needs a way to define block names from RGMB mesh generators for each region ID, as lumping all blocks in the mesh into just two blocks - one for tri elems and one for quad elems - is not sufficient. The ability to define custom block names through RGMB mesh generators currently exists, but this is a manual process and can be cumbersome for larger meshes. The option to automatically do this based on the region ID of the element would streamline this process.

Design

Add a parameter region_id_as_block_name in ReactorMeshParams, which will act as a global variable within the RGMB system to inform RGMB MG's that the block name should be defined as <RGMB_PREFIX>_REG_<REGION_ID>. If the element is a tri element, the suffix "_TRI" will be added.

Impact

More flexible workflows that can be used by Griffin directly. Currently, the workaround to enable such functionality is to instead define an additional MG in Griffin to convert extra element id's to block id's

@shikhar413 shikhar413 added the T: task An enhancement to the software. label May 20, 2024
shikhar413 added a commit to shikhar413/moose that referenced this issue May 20, 2024
shikhar413 added a commit to shikhar413/moose that referenced this issue May 20, 2024
pbehne pushed a commit to pbehne/moose that referenced this issue Jun 4, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
T: task An enhancement to the software.
Projects
None yet
Development

No branches or pull requests

1 participant