Join GitHub today
GitHub is home to over 36 million developers working together to host and review code, manage projects, and build software together.Sign up
Tapering off qubits using stabilizer conditions. #516
This module tapers off qubits given a set of stabilizers.
The module allows the user to:
The module comes with documentation and test module.
Xavier Bonet-Monroig and Mark Steudtner
Thanks for your pull request. It looks like this may be your first contribution to a Google open source project (if not, look below for help). Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).
Once you've signed (or fixed any issues), please reply here (e.g.
What to do if you already signed the CLA
So there's good news and bad news.
Note to project maintainer: This is a terminal state, meaning the
Hi @ncrubin ,
After yesterday's commit I saw in the CI that one of the test was failing in the python2.7 version because I was defining it as an empty list, after changing the mutable variables to None.
I updated the test module that includes the new possible case, and change the old one.
Edit: Again the CI fails on the same test. I will try to solve this to make it full compatible with python 2.7.
Edit2: It seems that CI is failing in the python 2.7 version. From what I get from the logs the error comes because the test module does not recognize StabilizerError (instead returns TypeError).
I'm really sorry for not being active on this lately.
I manage to narrow down that the test fail in python 2.7. I am suspicious that the fail is due to our customize error messages but I have seen code within OpenFermion with customize errors.
Currently I'm building an environment with 2.7 to see if I can reproduce the issue outside the test module.
Please, let me know if you have heard about similar issues before and how to address them.
Update: Found issue with customize error classes in python2, the super()init() does not work properly and one must use Exception.init() to initialize the inherent class.
Hi @ncrubin ,
As far as I understand, the coveralls counts how many new lines are used in the test module. We have tested all possible issue in the main functions, this implies that internal functions are indirectly tested. Do we have to also cover internal functions?
Thanks for the assistance.