-
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
Allowing to define an array varible with component size one #19567
Allowing to define an array varible with component size one #19567
Conversation
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.
- Add a test. Array diffusion with a variable with one component is sufficient.
- is_av/av -> array. FV is well known. AV is not
@loganharbour Thank you for super quick review! |
Timed out well with watching tv 😆 I’m good with all of this and understand the purpose - we just need to be stringent given that these chunks of code are ran in almost every use of moose |
Job Documentation on 49b4b02 wanted to post the following: View the site here This comment will be updated on new commits. |
Job Coverage on 49b4b02 wanted to post the following: Framework coverage
Modules coverageChemical reactions
Contact
Heat conduction
Navier stokes
Phase field
Richards
Full coverage reportsReportsWarnings
This comment will be updated on new commits. |
92b1697
to
1182e21
Compare
1182e21
to
a91f78e
Compare
Changes
|
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.
array_variable
->array
- Clean up
determineType
(remove redundant parameter) - Move error check to a better location and add a test for it
I'm good after this!
test/tests/variables/array_variable/array_variable_size_one_test.i
Outdated
Show resolved
Hide resolved
test/tests/variables/array_variable/array_variable_size_one_test.i
Outdated
Show resolved
Hide resolved
a91f78e
to
0c178c0
Compare
Job Precheck on 0c178c0 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:
|
0c178c0
to
f4bc80c
Compare
f4bc80c
to
e70955b
Compare
@lindsayad can you take a look at this please - I know that you're the one that did most of the variable cleaning and I would like a 👍🏼 or 👎🏼 on the |
I think that we will also want to add
in but I'd like a ✅ from @lindsayad on that one too |
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.
I would kind of like to see a coverage report, but this looks fine to me
@lindsayad good for another review - I thought that we might of broke something, but we didn't. Decided to keep the test that I made anyway This basically tests creating an array variable from 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.
👍 pending a favorable coverage report
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.
Coverage is favorable.
Docs failure is unrelated and patch is currently in bison devel
@yjung-anl can you update Griffin really quick to use the new function? |
closes #19564