Restrict Split2QUnitaries
to run on UnitaryGate
s only (backport #13095)
#13097
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 remaining problems with #12970.
Details and comments
If we run
Split2QUnitaries
with an incomplete 1-q basis gate set, we can end up in the situation where a supported gate is split into 2UnitaryGate
objects that might not be representable in the current basis gate set. For exampleThis PR fixes the behavior by only running on
UnitaryGate
objects -- hence not changing the gate types existing in the circuit.This is an automatic backport of pull request #13095 done by [Mergify](https://mergify.com).