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

See which apps will fail with the new skip-initial-residual-evaluation behavior #26222

Closed

Conversation

hugary1995
Copy link
Contributor

This PR is the counterpart of #23472, where use_legacy_initial_residual_evaluation_bahavior is set to false in MooseApp.C, so that we can see which apps will fail with the new behavior.

Once the tests are done, I'll tabulate the failed apps.

@loganharbour

This PR deprecates the parameter `compute_initial_residual_before_preset_bcs` in favor of
`use_pre_initial_residual`.

The user should set this parameter to true if they really want to use the pre-initial residual in the relative convergence check.

The pre-initial residual is defined as the norm of the residual evaluated at the beginning of the time step before any solution-modifying object is executed.
Solution-modifying objects are the objects that can potentially modify the solution vector. Currently, solution-modifying objects that are accounted for include:
- preset BCs
- constraints
- predictors

If the user does not explicitly ask to use the pre-initial residual, the pre-initial residual evaluation will be entirely skipped.
Even if the user asks for that, the pre-initial residual evaluation will be skipped if there is no active solution-modifying objects.
This behavior is consistent with the original discussion in the referenced issue.

See NonlinearSystemBase::shouldEvaluatePreinitialResidual() for the logic behind this. And please help me double check my logic.

close idaholab#10464
@moosebuild
Copy link
Contributor

Job Documentation on e3a8049 wanted to post the following:

View the site here

This comment will be updated on new commits.

Copy link

This pull request has been automatically marked as stale because it has not had recent activity in the last 100 days. It will be closed in 7 days if no further activity occurs. Thank you for your contributions.

@github-actions github-actions bot added the stale PRs that have reached or exceeded 90 days with no activity label Mar 11, 2024
@github-actions github-actions bot closed this Mar 19, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
stale PRs that have reached or exceeded 90 days with no activity
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants