-
Notifications
You must be signed in to change notification settings - Fork 436
Abort run by default on SCF convergence failure #3148
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
Conversation
|
Oh wow, how did you format all our test input files? Should we maybe make that a separate commit so we can later add it to .git-blame-ignore-revs? |
No objections. |
|
To separate out the actual changes you could try |
Got two patch files ... ? |
|
I was thinking you could do something like this:
|
|
Step 3 was not an automated process, because I still edited all files by hand. |
Ok, I think I found a way. Please do not merge. |
The new keyword IGNORE_CONVERGENCE_FAILURE can be set to obtain the old permissive behaviour. It replaces the keyword NOTCONV_STOPALL which enforced until now the strict behaviour which is now the default.
@oschuett Thanks for the patch file. The test is clean now after some minor fixes. OK to merge? |
|
Yes, all good. This nicely solves a long standing usage pitfall. |
| dft_control%qs_control%cdft_control%total_steps = & | ||
| dft_control%qs_control%cdft_control%total_steps + total_steps | ||
|
|
||
| IF (.NOT. converged) CPWARN("SCF run NOT converged") |
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.
Maybe we should keep the old warning message? I'd expect it's hard coded in many places.
The new keyword IGNORE_CONVERGENCE_FAILURE can be set to obtain the old permissive behaviour. It replaces the keyword NOTCONV_STOPALL which enforced until now the strict behaviour which is now the default.