-
Notifications
You must be signed in to change notification settings - Fork 1k
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
Group mesh-modifying user objects into a specific mesh modifier / other name syntax #27671
Comments
Thoughts on the names?
|
If I get this right, in the future this would have the ability to call Mesh System objects like |
Either we use those. (could be tricky, there's a lot that goes in the [Mesh] block) Personally I am leaning into making a new system. See the list of reasons in the initial post |
It would be interesting to see the return of |
@idaholab/moose-ccb |
My vote would be This could be a thrust area. See some potentially related discussion: #23371 |
I'd agree. |
Motivation
@dschwen @hugary1995 and others have built up quite a bit of capabilities in UOs that modify the mesh. This could be consolidated into a system / dedicated syntax for:
Design
Either:
This would likely involve:
The tradeoff is likely (partial) code duplication (2) vs code complexity (1).
This will likely involve:
Cool things with (2) that make me thing it is the way:
Note that there is some overlap between this and Executor capabilities. We are considering Executor mesh-modification / adaptivity and this new system would be related. It's more straightforward to do this than push people to Executors for this imo.
Impact
Easier for users to see our whole array of in-simulation mesh-modification capabilities
Easier for user-devs to contribute and add what they need inside a dedicated system
The text was updated successfully, but these errors were encountered: