possible inconsistency in units of cell and positions #12
-
Thanks for making the code available, really nice. Is there a possible inconsistency in the way that units are parsed for the cell and for the positions when using read_frames_cp2k? The function takes in the positions in Angstroms but the cell in bohr. I might have missed if this is already documented in the code. Anyway, changing to Angstrom as default for the cell in cp2k might help others not to encounter the same problem. |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 1 reply
-
There is a method to the madness, but it should be better documented, so we will do that - thank you for bringing it up. The idea is that all data within AML itself is in atomic units. Units in external files are determined either by the format itself, by convention (position data in XYZ, for example), or by whatever a specific program does. As
|
Beta Was this translation helpful? Give feedback.
There is a method to the madness, but it should be better documented, so we will do that - thank you for bringing it up.
The idea is that all data within AML itself is in atomic units. Units in external files are determined either by the format itself, by convention (position data in XYZ, for example), or by whatever a specific program does. As
read_frames_cp2k
gets the name of an XYZ file produced by CP2K, that has to be in angstrom, but internally, the position data is converted to atomic units after being read. If there is a cell provided to the function by hand, that has to be in atomic units, as it is AML data directly in Python. You can easily grab the factor fromaml.constants
and …