You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Recent changes and discussions (such as #492, #513, and #520) have highlighted the need for a generalizable way to transform ASE atoms objects into torch_geometric Data objects. Such a class would effectively replace AtomsToGraphs.
It would be useful if this function was capable of including many different properties without adding tons of keyword arguments (the way AtomsToGraphs currently has r_energy, r_forces, r_pbc, etc.). It may even be possible to include arbitrary properties. Perhaps it could use the new metadata guesser in some way?
This functionality would reduce the entry barrier for people building models/trainers for properties other than officially supported ones (energy and forces). It would also be good from a code readability standpoint since, in practice, AtomsToGraphs is currently most often used for things other than turning atoms into graphs.
The text was updated successfully, but these errors were encountered:
Recent changes and discussions (such as #492, #513, and #520) have highlighted the need for a generalizable way to transform ASE atoms objects into torch_geometric Data objects. Such a class would effectively replace AtomsToGraphs.
It would be useful if this function was capable of including many different properties without adding tons of keyword arguments (the way AtomsToGraphs currently has r_energy, r_forces, r_pbc, etc.). It may even be possible to include arbitrary properties. Perhaps it could use the new metadata guesser in some way?
This functionality would reduce the entry barrier for people building models/trainers for properties other than officially supported ones (energy and forces). It would also be good from a code readability standpoint since, in practice, AtomsToGraphs is currently most often used for things other than turning atoms into graphs.
The text was updated successfully, but these errors were encountered: