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

Need a DomainUserObject #19995

Closed
YaqiWang opened this issue Jan 10, 2022 · 1 comment · Fixed by #21217
Closed

Need a DomainUserObject #19995

YaqiWang opened this issue Jan 10, 2022 · 1 comment · Fixed by #21217
Assignees
Labels
C: Framework P: normal A defect affecting operation with a low possibility of significantly affects. T: task An enhancement to the software.

Comments

@YaqiWang
Copy link
Contributor

Reason

We need a new type of user object, with temporary name DomainUserObject (better name suggestions are welcome). This new user object is defined still on subdomains, but it can contain operations on elements and all sides (including boundary sides, internal sides and internal boundary sides). We want this DomainUserObject because we have needs to gather information in one place based on elemental and side quantities. Without this user object, we would need four separate user objects: one elemental user object, one internal side user object, one side user object and one general user object. It is quite tedious to manage these four user objects together, such as valid parameters, the same execute_on, etc.

Design

Adding this DomainUserObject can possibly be done with existing warehouse capabilities. Changes in ComputeUserObjectsThread.C are also expected. Currently we do not need to handle operations on nodes. Griffin developers can possible help on this. Tag @jthano.

Impact

A new capability.

@YaqiWang YaqiWang added the T: task An enhancement to the software. label Jan 10, 2022
@loganharbour loganharbour added C: Framework P: normal A defect affecting operation with a low possibility of significantly affects. labels Jan 10, 2022
@lindsayad
Copy link
Member

I was trying to find this last week but wasn't able to. Thanks for pointing me here!

@lindsayad lindsayad self-assigned this Jun 6, 2022
lindsayad added a commit to lindsayad/moose that referenced this issue Jun 6, 2022
lindsayad added a commit to lindsayad/moose that referenced this issue Jun 14, 2022
YaqiWang pushed a commit to YaqiWang/moose that referenced this issue Jun 17, 2022
lindsayad added a commit to lindsayad/moose that referenced this issue Jun 23, 2022
YaqiWang added a commit to YaqiWang/moose that referenced this issue Jul 9, 2022
YaqiWang added a commit to YaqiWang/moose that referenced this issue Jul 9, 2022
YaqiWang added a commit to YaqiWang/moose that referenced this issue Jul 9, 2022
YaqiWang added a commit to YaqiWang/moose that referenced this issue Jul 9, 2022
YaqiWang added a commit to YaqiWang/moose that referenced this issue Jul 9, 2022
YaqiWang added a commit to YaqiWang/moose that referenced this issue Jul 9, 2022
YaqiWang added a commit to YaqiWang/moose that referenced this issue Jul 9, 2022
YaqiWang added a commit to YaqiWang/moose that referenced this issue Jul 9, 2022
YaqiWang added a commit to YaqiWang/moose that referenced this issue Jul 9, 2022
YaqiWang added a commit to YaqiWang/moose that referenced this issue Jul 9, 2022
YaqiWang added a commit to YaqiWang/moose that referenced this issue Jul 10, 2022
YaqiWang added a commit to YaqiWang/moose that referenced this issue Jul 10, 2022
YaqiWang added a commit to YaqiWang/moose that referenced this issue Jul 11, 2022
jain651 pushed a commit to jain651/moose that referenced this issue Oct 31, 2022
jain651 pushed a commit to jain651/moose that referenced this issue Oct 31, 2022
jain651 pushed a commit to jain651/moose that referenced this issue Oct 31, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
C: Framework P: normal A defect affecting operation with a low possibility of significantly affects. T: task An enhancement to the software.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants