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 diagonalization errors handler to ph base workchain #757

Merged
merged 3 commits into from
Nov 24, 2021

Conversation

unkcpz
Copy link
Member

@unkcpz unkcpz commented Nov 23, 2021

This is the quick workaround before PR #756, the base stdout parsing by @mbercx get finished and merged.

This PR fixes two issues of Ph calculation: a) when the calculation failed without 'Job Done' in the output file, the error was not caught and the calculation will be finished with exit status 0. b) add a handler to 'problems computing cholesky' failed calculation.

Copy link
Contributor

@sphuber sphuber left a comment

Choose a reason for hiding this comment

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

All good, thanks @unkcpz !

@sphuber sphuber merged commit 3807e8c into aiidateam:develop Nov 24, 2021
@unkcpz unkcpz deleted the fix/catch-ph-imcomplete-error branch November 24, 2021 09:51
bastonero pushed a commit to bastonero/aiida-quantumespresso that referenced this pull request Dec 20, 2021
)

The `PwBaseWorkChain` now has a handler for `ERROR_COMPUTING_CHOLESKY`,
an exit code that was added to `PhCalculation` which is returned if the
calculation failed due to problems with cholesky factorization. The
handler will switch to `cg` diagonalization and restart the calculation.
If the diagonalization already was `cg` it will abort.

The `PhParser` was also fixed to return `ERROR_OUTPUT_STDOUT_INCOMPLETE`
in case the stdout was incomplete and no other more specific errors were
detected.
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.

2 participants