All notable changes to this project will be documented in this file.
The format is based on Keep a Changelog, and this project adheres to Semantic Versioning.
0.15.3 - 2022-07-20
- version bump due to pypi error
0.15.2 - 2022-07-20
- Changed pyquatools dependency to be latest
0.15.1 - 2022-06-30
- Resolved bug in migration code for paramstore due to namespace changes.
0.15.0 - 2022-06-26
- Dashboard now supports marking experimental results as favorite. This is added to DB as well.
- QuAM now supports kwargs to set the location of a remote QuantumMachineManager
0.14.0 - 2022-06-22
- Flame: expose terminate_node from nodeio
- Flame: hotfix, incread default timeout value for inital connection.
- paramstore: Params now have description & node_id attributes settable in set_param()
- paramstore: InProcessParamStore multi-processing-safe using lock file
0.13.0 - 2022-06-19
- Flame: Support for saving single node dry-runs into EntropyHub
- Flame: Support for specifying username and password for message queue via environment variables
- DB Migration for removing duplicate data from HDF5 and SQLite
- Single node dry run in Flame
- Resolved high CPU issue when running the dashboard in Linux (#282)
- Entropy serve CLI command now reports the serve path on the STD-IO
- spinner displayed while plots are loading for a selected experiment
- Caching of the
FigureRecordsin memory, Reducing the time to re-render plot tabs significantly.
- Expiration field for parameters in paramstore (prep for calibration automation)
- Project size and remaining HDD space is now shown in header row
- Readme files pushed into modules folders
- Results dashboard layout changed to column view
- Support for Jupyter notebook node development in NodeIO
- Added Flame execution engine with NodeIO library
- Updated QuAM names
0.7.0 - 2022-05-31
- Added a --debug flag to CLI
- Added migration for paramStore v0.2
- QuAM - Quantum Abstract Machine. An abstraction layer above qubits to help to build and run experiments. This is a first implementation of this tool.
0.5.6 - 2022-05-23
- ParamStore GUI now looks for param.db file in .entropy folder
- ParamStore GUI tags are now editable and correctly displayed
0.5.5 - 2022-05-16
- ParamStore viewer added to the GUI
- Added Quantum Abstraction Machine (QUAM)
- Success/Failure filter in results table is broken. A bug was issued
0.5.4 - 2022-05-08
- Data now save in HDF5 file per experiment
0.5.3 - 2022-05-02
- Added methods to change key name and list tags per key in param store
0.5.2 - 2022-04-25
- Resolved a problem with logging errors occurring in entropy nodes
0.5.1 - 2022-04-13
- Dashboard: changed plotting interface
- DB: retrieving data based on node ID is fixed
0.5.0 - 2022-03-01
- add retry behavior for nodes - recovery from errors
- When serving the Results Dashboard, Dash's "dev tools" feature is always enabled.
- added a paramStore: a mechanism for saving system state with a git-like interface
0.4.1 - 2022-01-23
- Dashboard: Fixed auto plot to support Dict results
0.4.0 - 2022-01-11
- New results dashboard web application
- Dashboard: Auto plot last result
- Dashboard: Serve using production-grade WSGI server (waitress 2.0.0)
- Dashboard: Experiments table is refreshed from disk every 3 seconds
0.3.0 - 2021-10-11
- Entropy now is also a CLI utility see doc here.
- CLI utility to help upgrade the entropy project.
- Entropy project is now a directory with
.entropysubdirectory with all entropy specific information.
0.2.0 - 2021-09-30
- New HDF5 support for data persistence
0.1.2 - 2021-06-07
- Pass "save results" as parameter for node, enabling to toggle data saving
0.1.1 - 2021-05-11
- Package metadata
0.1.0 - 2021-05-10
- Directed Graph for experiment authoring - This is the hallmark feature of Entropy which enables breaking down an experiment into a graph of nodes which can run arbitrary code and pass data from node to node.
- Resource management - nodes in a graph share resourced which can be, but are not limited to, lab instruments. This allows easy usage of resources and sharing of information as well as persistence of state and automated saving of metadata representing the state of the entire lab.
- Data saving backend - Node data, and resource state data, is saved to a DB backend. This release support saving to a SQLite DB. The backend is extendable and additional persistence targets can be added.
- QCodes driver library adapter - an adapter for the drivers provided by QCodes to be easily used with the Entropy persistence backend.
- QPU-DB - This is an extension to entropy which is built to save and manage the pieced of information describing a Quantum Processing Unit. If multiple nodes are set up to calibrate the QPU, measuring decoherence times and resonant frequencies for example, then that data can be saved to a centralized store and subsequently used in the target application. Warning: this module will be replaced in future releases but a migration path will be provided.