Fix post-oxidization change in ConsolidateBlocks
behavior (backport #13450)
#13453
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
Fixes the behavioral difference introduced by #13368 that caused #13438.
The original implementation of the pass used to set the
ConsolidateBlocks
internal decomposer callingunitary_synthesis._decomposer_2q_from_basis_gates
, which, whenkak_basis
wasn't found, would returnNone
. During the oxidization efforts,unitary_synthesis._decomposer_2q_from_basis_gates
was replaced with inline code that didn't contemplate this path (always set a default decomposer), which in the reproducing example lead to a longer output circuit (the gates were collected into a unitary block and then decomposed differently).Details and comments
Technically not a bugfix because the change wasn't released yet.
Using the example shown in the issue ->
ConsolidateBlocks
output dag with 1.2.4:ConsolidateBlocks
output dag with 1.3.0rc1:ConsolidateBlocks
output dag after this fix:This is an automatic backport of pull request #13450 done by [Mergify](https://mergify.com).