Fixed block collection with classical conditions in Collect2QBlocks #2956
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.
Summary
As revealed in the random testing there was a niche bug in Collect2QBlocks that lead to blocks of 3 qubits being collected. This occured because the predeccessors/successors of the nodes were added using the calls
predecessors()
andsuccessors()
rather thanquantum_predecessors()
andquantum_successors()
. This meant that if there was a pred/succ node that shared the same classical register, but was not acx
node it could be added despite potentially not sharing the same qubits as the node currently being looked at.As it is blocks of quantum gates we are looking for, it makes sense to only look at the quantum successors/predecessors.
Details and comments
Solved by replacing all the relevant calls.
NB there are still some calls to
predecessors()
andsuccessors()
as these calls are looking at the ordering of the nodes, so they need to take into account any classical aspects as well as quantum.