-
Notifications
You must be signed in to change notification settings - Fork 36
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Incompatibility with pymatching #276
Comments
There was a major version release for pymatching yesterday: https://github.com/oscarhiggott/PyMatching/releases/tag/v2.0.0 you'll probably need to update the usage for the new version, or in the short term pin the version < 2.0 until you update the usage. |
I've now fixed this issue in pymatching in this PR and made a new patch release (v2.0.1) that includes the fix. The issue was that I wasn't handling the case that the user adds a detection event on the boundary node in v2.0.0. There's never any need to add detection events to boundary nodes, as the boundary is handled automatically by the decoder. But now these boundary node detection events are ignored, as they were in v0.7. I also just opened PR #280 which fixes a couple of minor remaining issues caused by the upgrade to v2.0.1. See the PR for details. PR #280 is intended to replace #278. |
Thanks @oscarhiggott! |
Steps to reproduce the problem
Run tests.
What is the current behavior?
Multiple tests involving PyMatching are failing.
The text was updated successfully, but these errors were encountered: