Zero out syndrome in the support of UserGraph boundary nodes #40
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fixes an issue where adding a detection event on a node marked as a boundary node in the Python API led to:
E.g. This breaks tests in qiskit-qec: qiskit-community/qiskit-qec#276
The fix is just to zero out the syndrome in the support of these boundary nodes, since the algorithm already handles the boundary correctly without these additional detection events.