ENH: Roadmap for merging Trajectory and BundleTrajectory
After discussion with @jensj we agreed that it would be nice to merge the Trajectory and BundleTrajectory formats so the BundleTrajectory is implemented by a different backend.
Suggested roadmap:
-
Merge merge-request !351 (merged) so that new BundleTrajectories are written in a format that can be read by the new backend.
-
Update Trajectory so it has the extra functionality of BundleTrajectory
-
User can control what data is written in every frame, in the first frame only, or not at all.
-
Allow the user to add extra data which can either come from the arrays dictionary, or from a user-supplied source.
-
Allow varying number of atoms from frame to frame. This will break ase-gui plotting, and should perhaps result in a stern warning, but can be useful for some kinds of simulations.
-
-
Implement the new backend so it saves in a format very similar to BundleTrajectory, and is able to read the BundleTrajectory files (with Ulm backend).
-
Make a tool converting BundleTrajectories from Pickle backend to Ulm backend (in place).
-
Officially deprecate BundleTrajectory.