PwBaseWorkChain
: do no assume output_band
exists in band sanity check
#544
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fixes #543
The
output_band
output of thePwCalculation
is optional and, forexample, when the setting
no_bands=True
, the band files will not beretrieved and consequentially not parsed. The process handler checking
the bands
sanity_check_insufficient_bands
, however, assumed the outputnode is always there. This is changed to simply skip the check if the
node is not there.
Note that we do not check in the work chain whether the output should
have been there, because the sanity check is only triggered for
successful calculations, and if the output should have been there, the
calculation should have been failed. If this is not the case, that is a
bug in the parser and should be addressed there.