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
It would be nice if ILI could work with an MDTraj trajectory, rather than ASE atoms. For processing trajectories, constructing ASE atoms for each frame seems wasteful. I don't mind atoms as an alternative if you think it's useful. Possibly even better - we could again separate specific "formats" of input from just feeding individual arguments to the constructor.
The text was updated successfully, but these errors were encountered:
AFAICT, you need not construct individual atoms objects for each snapshot in a trajectory. It should work by just updating the positions. However, I agree that working on and MDTraj object would have some advantages.
Let's keep the issue open, so that we don't forget and can come back to it, later
It would be nice if
ILI
could work with an MDTraj trajectory, rather than ASE atoms. For processing trajectories, constructing ASE atoms for each frame seems wasteful. I don't mind atoms as an alternative if you think it's useful. Possibly even better - we could again separate specific "formats" of input from just feeding individual arguments to the constructor.The text was updated successfully, but these errors were encountered: