Skip to content

Conversation

@magnoxemo
Copy link

@magnoxemo magnoxemo commented Aug 27, 2025

closes #1200 and #1127

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"
Copy link
Collaborator

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.

@moosebuild
Copy link
Collaborator

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
You can directly apply the patch by running, in the top level of your repository:

curl -s https://mooseframework.inl.gov/cardinal/docs/PRs/1201/clang_format/style.patch | git apply -v

Alternatively, with your repository up to date and in the top level of your repository:

git clang-format 9810264131e80cf841fb6212c8abec025d4544f2

type = Exodiff
input = example_input.i
exodiff = example_input_out.e
requirement = "The system shall reproduce the clustering pattern by evaluating a
Copy link
Collaborator

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! :)

@aprilnovak
Copy link
Collaborator

I realize now that this PR is actually quite consistent with referring to the variable data as a score. I left a few comments which changed that to value, but perhaps it's worth discussing the name and ignoring my name changes. I could envision a world where we use variable data which might not refer to a tally in which case perhaps value is a bit more generic and recognizable. What do you think? @magnoxemo @nuclearkevin @gonuke

}
// check if mesh is replicated. If not then throw a moose error.
if (!_mesh.is_replicated())
mooseError("Mesh must be replicated");
Copy link
Collaborator

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?

Copy link
Author

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>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Add heuristic based user obejct for clustering

5 participants