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

New error when two different ICs are specified #29672

Merged
merged 4 commits into from
Jan 22, 2025

Conversation

DanielYankura
Copy link
Contributor

-Error thrown if an initial_condition parameter is provided along with an initial_from_file_var parameter for the same variable.

closes #20944

Reason

This added error check will make debugging input files easier.

Design

Previously an error was only thrown if two initial_condition parameters were supplied for the same variable. Now an error is also thrown if an initial_from_file_var is also provided.

Impact

@moosebuild
Copy link
Contributor

moosebuild commented Jan 10, 2025

Job Documentation, step Docs: sync website on af85c85 wanted to post the following:

View the site here

This comment will be updated on new commits.

Copy link
Contributor

@GiudGiud GiudGiud left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Good idea!

framework/src/actions/AddVariableAction.C Outdated Show resolved Hide resolved
@GiudGiud GiudGiud self-assigned this Jan 10, 2025
@DanielYankura
Copy link
Contributor Author

DanielYankura commented Jan 14, 2025

So the other day I noticed there was one test that was failing with this new error message, and that was the restart/restart_diffusion.restart_error_with_ics test since my new error will get thrown before checkICRestartError does. The only case I could find where this doesn't happen is if you have two variables with one being restarted while the other is given an initial condition. If that is something we want to test for I can go ahead an modify that one test to have two variables instead. If not I have a few ideas for modifying my error check so that it doesn't interfere with the other one.

@GiudGiud
Copy link
Contributor

GiudGiud commented Jan 14, 2025

you ll have to modify that test to hit the error, but through a different code path since you covered this one

so yes the 2 variables idea is good!

@GiudGiud
Copy link
Contributor

GiudGiud commented Jan 14, 2025

let's squash formatting commits with the commit introducing the formatting problem

or (and) even better, install the format hooks (see scripts/) to avoid failing the precheck

@moosebuild
Copy link
Contributor

moosebuild commented Jan 15, 2025

Job Coverage, step Generate coverage on af85c85 wanted to post the following:

Framework coverage

bf7a39 #29672 af85c8
Total Total +/- New
Rate 85.25% 85.25% +0.00% 100.00%
Hits 108117 108122 +5 5
Misses 18713 18713 - 0

Diff coverage report

Full coverage report

Modules coverage

Coverage did not change

Full coverage reports

Reports

This comment will be updated on new commits.

DanielYankura and others added 4 commits January 21, 2025 22:51
-Error thrown if an initial_condition parameter is provided along with an initial_from_file_var parameter for the same variable.

closes idaholab#20944
-error message is worded more clearly now
-initial_from_file_var is now a transfer param
-test was updated to reflect new error message
@GiudGiud
Copy link
Contributor

Failures are two unrelated timeouts. @DanielYankura if you're ok with the change I ll merge

@DanielYankura
Copy link
Contributor Author

Sounds good. I took a look over the changes you made and I am good with them if you want to merge!

@GiudGiud GiudGiud merged commit 9f9441f into idaholab:next Jan 22, 2025
48 of 51 checks passed
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.

No error or warning on specifying two different initial conditions
3 participants