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.
Summary
The
datar
from a PotentialField was erroneously being rescaled upon loading. the fields provided by abinit are intensive, but unlike the density, they are not defined "per unit volume". Thus, no rescaling from the default length format (Bohr radii) to the default Pymatgen format (Angstrom) is required.Beforehand, this would be the plane-averaged total potential of an 11-layer aluminium slab cut along (100) and referenced to the Fermi level:
here one would mistakenly infer that the work function of this slab is almost 50 eV.
This is the result with the corrected code:
Reaching a work function of approximately 4.2 eV, consistent with the literature for 11-layer slabs with the PBE functional.
As a minor detail, the code now loads the only two type conversions
bohr_to_angstrom
andHa_to_eV
that are being used.