Save/restore information between sessions

[prjemian]

A user request is to save local information to a file for later restore. The file content might be a dictionary (key: value pairs).

The file would be updated automatically as local value changes. We'd need multiple instances, for system, for user A, user B, user C with settings 1, 2, and 3, ...

We'd need to decide when to load these, and which ones to load by default on startup.
We also need to handle different types of local information (Python variable, ophyd device/signal, EPICS PV).

We need a backend file handler for this. Choice of file format is not important to us (at least now). Human readable (& editable) is not an initial concern. Maybe later.

[prjemian]

@strempfer Thanks for the idea!

[prjemian]

The class should provide a dict-like API to the user and handle automatically the backend file storage.

[prjemian]

This enhancement is prompted by the Sardana Door feature which allows for different configurations (based on ipython profile?). Still trying to find what, exactly, such a configured file looks like.

[prjemian]

Similar idea to diffractometer configuratio:

• Store operational information locally for use outside of bluesky bluesky/hklpy#256
• standardize export & restore of diffractometer configuration bluesky/hklpy#279

[prjemian]

@strempfer - The default bluesky setup already saves the RunEngine metadata to local storage and the diffractometer configuration can be saved via the new code in hklpy. Is there other information to be saved and restored?

[prjemian]

On discussion with @strempfer, bluesky/hklpy#279 and related work will satisfy this request.