Allow (de)serialization of device elements

Fabio Grigolorequested to merge
se-624-deserialize-device-elements into main

Explanation of changes

This MR allows one to serialize and deserialize DeviceElement and its instances, e.g. BasicTransmonElement, BasicElectronicNVElement, BasicSpinElement. I also took the liberty of refactoring the to_json and from_json methods, as well as their _file counterparts, to a separate mixin so it could be reused in both QuantumDevice and DeviceElement class definitions.

Motivation of changes

I figured we might be requested to (de)serialize other elements in the future using SchedulerJSON[En|De]coder.

Merge checklist

See also merge request guidelines

  • Merge request has been reviewed (in-depth by a knowledgeable contributor), and is approved by a project maintainer.
  • New code is covered by unit tests (or N/A).
  • New code is documented and docstrings use numpydoc format (or N/A).
  • New functionality: considered making private instead of extending public API (or N/A).
  • Public API changed: added @deprecated and entry in deprecated code suggestions (or N/A).
  • Newly added/adjusted documentation and docstrings render properly (or N/A).
  • Pipeline fix or dependency update: post in #software-for-developers channel to merge main back in or update local packages (or N/A).
  • Tested on hardware (or N/A).
  • CHANGELOG.md for breaking changes and AUTHORS.md have been updated (or N/A).
  • Update Hardware backends documentation if backend interface change or N/A
  • Check whether performance is significantly affected by looking at the Performance metrics results.
  • Windows tests in CI pipeline pass (manually triggered by maintainers before merging).
    • Maintainers do not hit Auto-merge, we need to actively check as manual tests do not block pipeline

For reference, the issues workflow is described in the contribution guidelines.

Edited by Fabio Grigolo

Merge request reports