-
Notifications
You must be signed in to change notification settings - Fork 45
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Use device-specific gatesets for transpilation #141
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
- Requested few straightforward changes (hopefully).
- Tests are missing.
- we could close Decompose circuits onto the native gate set of the backend #138
As far as tests go, the existing tests actually cover the implementation changes, since the transpiler target gatesets change in the tests too; an incorrect translation will lead to mismatch between the Aer and Braket simulations. |
Alright, approving but feel free to give some thoughts about #141 (comment). As for the tests, you are right. I just feel a bit uncomfortable that the transpiler mixes everything and our tests become less specific. |
Summary
Right now, the adapter transpiles circuits to a target gateset of all gates supported by Braket, which can cause problems if the device itself doesn't support a gate. This PR changes the adapter to transpile to the device's target gateset.
Details and comments
For devices that support control modifiers, named controlled gates that are not already in Braket will be translated to the corresponding uncontrolled gate with control modifiers applied.