Hello, i think it would be good to set the velocities per default on zero in the AtomsBase interface.
Yet, if one calls velocity(system) an error is returned if velocities are not determined in the loaded file.
In AtomsBase, if you create a system without creating velocities they are set on zero. This means you get a Vector of a Vector filled with zeros.
I think this would be a good adaptation. However, velocities would be written in the file, if the system is saved, even if they are just zero.
Maybe it would be a possibility to check in the write_dict function whether the velocities are just zero or not.
I would prefer not to include velocities by default - they are often not needed for many tasks. An error when one calls velocity(system) is an appropriate response
Hello, i think it would be good to set the velocities per default on zero in the AtomsBase interface. Yet, if one calls velocity(system) an error is returned if velocities are not determined in the loaded file. In AtomsBase, if you create a system without creating velocities they are set on zero. This means you get a Vector of a Vector filled with zeros. I think this would be a good adaptation. However, velocities would be written in the file, if the system is saved, even if they are just zero. Maybe it would be a possibility to check in the write_dict function whether the velocities are just zero or not.
What do you think about this?