Fix error in Target non-global operation method with ideal gates (backport #7554) #7561
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
![mergify[bot]](https://avatars.githubusercontent.com/in/10562?s=60&v=4){kind=small}
* Fix error in Target non-global operation method with ideal gates This commit fixes an issue in the Target get_non_global_operation_names() method. Previously this method would crash when you had a target with it's instruction properties set to None (which is typically used for an ideal simulator). * Fix issue with transpile() on BackendV2 with ideal operation This commit fixes an issue when running transpile() with a BackendV2 based backend that has ideal operation defined in it's target. A Target that has an operation with its qargs set as None means it's ideally defined on all qubits (or all combinations of qubits for >1 qubit operations). However, the pre-processing of the target in the transpile() method was not taking this into account and would fail if a backend with this set was used. * Tweak timing constraints parsing in transpile() In the previous commit there were some issues in the tweaks made to the transpile() function to parse the timing_constraints argument. The basic flow we wanted for the standalone target case is to create a TimingConstraints object directly from that Target. However, the internal function was expect only a dict was passed in and tried to create a TimingConstraints object from it. The previous commit tried to address this but neglected the standard use with a dict. This commit corrects this oversight and tweaks the logic to handle a predefined TimingConstraint object first and then fallsback to the other behavior. (cherry picked from commit fe5acd4)
jakelishman
added
automerge
Changelog: Bugfix
jakelishman
approved these changes
Jan 24, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This is an automatic backport of pull request #7554 done by Mergify.
Mergify commands and options
More conditions and actions can be found in the documentation.
You can also trigger Mergify actions by commenting on this pull request:
@Mergifyio refreshwill re-evaluate the rules@Mergifyio rebasewill rebase this PR on its base branch@Mergifyio updatewill merge the base branch into this PR@Mergifyio backport <destination>will backport this PR on<destination>branchAdditionally, on Mergify dashboard you can:
Finally, you can contact us on https://mergify.com