Upgrade and Downgrade

Whenever a breaking change happens MML tries to silently handle these internally (e.g. the switch from .yaml to .json format in storing ModelStorage, where loading old .yaml files is still possible). Occasionally breaking changes require an upgrade of the underlying MML_EXPS and MML_DATA directories. This is where the upgrade mode allows to switch versions with ease.

For example mml-core=0.12.0 changed the data backend, hence when coming from any version below an upgrade is necessary. This is performed via first upgrading mml-core to a version at least 0.12.0 and then calling.

mml upgrade mode.version=0.11.1

(if coming from version 0.11.1 before). The scheduler handles multiple upgrades internally so there is no need in upgrading step wise manually: simple upgrade mml-core to the most recent version and provide your previous version via mode.version.

If you want to downgrade the necessary steps are almost identical, but the order is reversed: With the current mml-core version call

mml downgrade mode.version=0.11.1

(if you want to downgrade your files to a 0.11.1 compatible version). And afterward downgrade mml-core itself.