-
Notifications
You must be signed in to change notification settings - Fork 66
add clustering user obejcts #1201
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
base: devel
Are you sure you want to change the base?
Conversation
adding eeid_adder
Co-authored-by: April Novak <novak@berkeley.edu>
| cli_args="--mesh-only" | ||
| expect_err="Both 'extra_element_integer_names' and 'values' cannot be empty. Please provide at least one param for each." | ||
| requirement="Number of entries in values needs to be equal to the number of extra_element_integer_names" | ||
| requirement="Number of entries in 'values' and 'extra_element_integer_names' must be nonzero" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
For SQA purposes, the requirement follows kind of specific conventions. These should be written as "requirements", like "The system shall error if the values for extra element integers is empty." For these RunException-type tests, some notion of the system erroring should be in the test requirement.
|
Job Precheck, step Clang format on 93f3bd1 wanted to post the following: Your code requires style changes. A patch was auto generated and copied here
Alternatively, with your repository up to date and in the top level of your repository:
|
doc/content/source/userobjects/ValueFractionHeuristicUserObject.md
Outdated
Show resolved
Hide resolved
doc/content/source/userobjects/ValueFractionHeuristicUserObject.md
Outdated
Show resolved
Hide resolved
doc/content/source/userobjects/ValueRangeHeuristicUserObject.md
Outdated
Show resolved
Hide resolved
doc/content/source/userobjects/ValueDifferenceHeuristicUserObject.md
Outdated
Show resolved
Hide resolved
test/tests/userobjects/clustering/execptions_and_warnings/tests
Outdated
Show resolved
Hide resolved
test/tests/userobjects/clustering/execptions_and_warnings/tests
Outdated
Show resolved
Hide resolved
test/tests/userobjects/clustering/execptions_and_warnings/tests
Outdated
Show resolved
Hide resolved
test/tests/userobjects/clustering/execptions_and_warnings/tests
Outdated
Show resolved
Hide resolved
| type = Exodiff | ||
| input = example_input.i | ||
| exodiff = example_input_out.e | ||
| requirement = "The system shall reproduce the clustering pattern by evaluating a |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is a perfectly-written test requirement! :)
|
I realize now that this PR is actually quite consistent with referring to the variable data as a |
| } | ||
| // check if mesh is replicated. If not then throw a moose error. | ||
| if (!_mesh.is_replicated()) | ||
| mooseError("Mesh must be replicated"); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Since you have two different mooseError which test for replicated mesh (one in this object, one in ClusterHeuristicUserObjectBase), you should technically have two tests isolating the objects so that you can cover both of these errors - if that is possible?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Agreed. I will add another test to catch this error.
Co-authored-by: April Novak <novak@berkeley.edu>
closes #1200 and #1127