Need mechanism for updating file schema from previous versions. about mdsynthesis HOT 5 CLOSED

For example, between 0.5.0 and the upcoming 0.5.1, the way selections are stored has changed from a Table to an Array (in PyTables parlance). This has changed the way the selection getters work for the SimFile such that selections stored the old way no longer work. The updater code needs to check for old-style selections and update them, leaving new-style selections alone. Only after it has finished everything should it update the version number of the statefile.

from mdsynthesis.

Moving this to the next release. Since the splitting out of datreant from mdsynthesis the versioning system itself has changed, so it would be a terrible hack to try and make this work for the pre-release schema. Each Sim now has a datreant version and a separate mdsynthesis version, giving the pieces needed for the update scheme to work in the next release.

The restructuring of the package makes room for the machinery we will need to make a smooth version updater, so for now we are good to go.

from mdsynthesis.

I think you can safely down-grade the priority, given that there isn't a full release yet.

from mdsynthesis.

@orbeckst I think so. :D

from mdsynthesis.

Closing for now. Not really necessary at the moment, and not having some checking every time a Sim is init-ed keeps them cheap to make.

from mdsynthesis.