From the context point of view, it is similar to #25
Where the VASP terminated the calculation, vasprun.xml is not complete, and we get the issue.
Steps to reproduce
(I'll link inputs which results to have this issue)
Expected behavior
Running them with same settings and resources, should cause VASP to throw similar behavior but VASP is unpredivtable. So, who really knows.
Your environment
Operating system: Centos (Salomon)
Resources: 4 nodes (96 cpus)
aiida-core version: 1.3.0
aiida-vasp version :1.0.1
aiida-bjm version: 0.3.0
Possible solution
Once we have the described mechanism in #25 , it should not happen (at least in the case of throwing parsin exception).
In order to solve the issue in VASP, it seems pretty scarce error with not much of information out there.
However, so far, I found that following solutions can remedy the issue:
Describe the bug
From the context point of view, it is similar to #25 Where the VASP terminated the calculation,
vasprun.xmlis not complete, and we get the issue.Steps to reproduce
(I'll link inputs which results to have this issue)
Expected behavior
Running them with same settings and resources, should cause VASP to throw similar behavior but VASP is unpredivtable. So, who really knows.
Your environment
1.3.01.0.10.3.0Possible solution
Once we have the described mechanism in #25 , it should not happen (at least in the case of throwing parsin exception). In order to solve the issue in VASP, it seems pretty scarce error with not much of information out there. However, so far, I found that following solutions can remedy the issue:
LREALtoFalse