Clearer description in generated KPOINTS comment line #1842
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.
Change k-points / atom to k-points / number of atoms
Summary
As mentioned in #1841, the comment line in the Pymatgen-generated VASP KPOINTS file is somewhat misleading. This PR changes it from being # kpoints/atom to # kpoints/number of atoms in the comment line, which is also consistent with what's on the Materials Project documentation. This should make it clearer that the number of k-points would be higher for smaller systems.
Perhaps worth noting: there is still the very minor ambiguity in that pymatgen.ext.jhu takes
kppra
as an input argument, whereaspymatgen.io.vasp.inputs.Kpoints.automatic_density()
takeskppa
as an input argument, but obviously the keywords should not be adjusted, and I think the documentation for the latter (which simply stateskppa
= grid density) is accurate without being confusing. Therefore, I did not make any changes to the documentation.