Closed Andrew-S-Rosen closed 2 years ago
Hi @arosen93. I feel a little guilty. I've fixed this bug and a few others in a branch I'm developing on: https://github.com/materialsproject/atomate2/tree/electron-phonon
Just so you know, there is another serious bug in the main branch, whereby changes to user_incar_settings sometimes don't get applied when the job runs.
Hopefully, this branch will stabilise within a day and then I'll merge into the main branch.
Sorry for the inconvenience!
Hi @utf, not a problem! I know that things are still being worked on. Good to know!
Edit: By the way, I noticed the user_incar_settings
issue in the main branch. Haven't had an issue while testing out your electron-phonon
branch! Feel free to close this issue when you get the branch merged.
Fixed in main branch.
Describe the bug Given the attached OUTCAR, I get
The Atomate2 job then fails as a result. This is on the current version of Atomate2.
To Reproduce
OUTCAR.txt
Solution
This is related to VASP 6.2.0+. First, as seen in the attached OUTCAR, sometimes VASP reports N/A for average memory used, and so Pymatgen converts this to
None
. The workaround solution in Atomate2 is to accept eitherfloat
orNone
(if that's not being done so already). The second issue regarding the number of cores can be fixed upstream in Pymatgen. I opened a PR here: https://github.com/materialsproject/pymatgen/pull/2308