You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Nov 16, 2023. It is now read-only.
The Magic Rounding scheme is currently only compatible with the (3,1,p) QRAC for encoding classical binary variables onto qubits. [...] We plan to make Magic Rounding compatible with additional encoding options in the future.
Let's improve magic rounding to work regardless of whether max_vars_per_qubit is 1, 2, or 3 (i.e., with all available encodings).
Once this is complete, we can also remove the _encoding attribute from the RoundingContext and enable the protected-access pylint check throughout the code base.
The text was updated successfully, but these errors were encountered:
* Add support for (1,1,p) and (2,1,p) QRACs
Addresses #7 .
* remove unused import
* handle (2,1,p)-encoded single dvar
* Remove caveat from README that is fixed by this branch
* Update magic rounding tests to be for (2,1,p) and (1,1,1) QRACs
* simplify (1,1,p)-qrac magic basis choice
Co-authored-by: Jim Garrison <jim@garrison.cc>
* comment qrac decoding
Co-authored-by: Jim Garrison <jim@garrison.cc>
* protect vars_per_qubit
* improve comment for op_index
* inplace=False
Co-authored-by: Jim Garrison <garrison@ibm.com>
Co-authored-by: Jim Garrison <jim@garrison.cc>
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
What is the expected enhancement?
As the README currently says:
Let's improve magic rounding to work regardless of whether
max_vars_per_qubit
is 1, 2, or 3 (i.e., with all available encodings).Once this is complete, we can also remove the
_encoding
attribute from theRoundingContext
and enable theprotected-access
pylint check throughout the code base.The text was updated successfully, but these errors were encountered: