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

add a check for nonlinear residual pingpong #16376

Closed
arovinelli opened this issue Dec 2, 2020 · 1 comment
Closed

add a check for nonlinear residual pingpong #16376

arovinelli opened this issue Dec 2, 2020 · 1 comment
Labels
P: normal A defect affecting operation with a low possibility of significantly affects. T: task An enhancement to the software.

Comments

@arovinelli
Copy link
Contributor

Reason

Sometimes, especially with structural simulations, the nonlinear residual starts pingponging.
Pinging means the residual starts fluctuating between two values.
When this happens, all the subsequent calculations are simply a waste of computational times.

Design

Add a parameter to the executioner block that will be used as a threshold value to kill the current timestep if nonlinear residual pingpong happens.
Add check for nonlinear residual pingpong inside FEProblemBase::checkNonlinearConvergence

Impact

No cons, just a new feature that will help to prevent computational time waste

@arovinelli arovinelli added P: normal A defect affecting operation with a low possibility of significantly affects. T: task An enhancement to the software. labels Dec 2, 2020
arovinelli pushed a commit to arovinelli/moose that referenced this issue Dec 2, 2020
@YaqiWang
Copy link
Contributor

YaqiWang commented Dec 3, 2020

Can this just be achieved by setting nl_max_its or the divergence tolerance? I am questioning because this sounds pretty specific and can confuse general users.

@fdkong fdkong closed this as completed in c0c8f0b Dec 9, 2020
jain651 pushed a commit to jain651/moose that referenced this issue Apr 19, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
P: normal A defect affecting operation with a low possibility of significantly affects. T: task An enhancement to the software.
Projects
None yet
Development

No branches or pull requests

2 participants