Adding the initial implementation for pauliexp gates support. #7374
Conversation
This file contains hidden or 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
github-actions
bot
added
size: M
…rg/Cirq into pauli-exponential-support
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.
The primary motivation for adding native Pauli‐exponential (pauliexp) support is performance - when we send pauliexp directly to IonQ, our compiler can optimize across a larger context (instead of first Trotterizing), which speeds up development and execution times. Allowing pauliexp to go through "as-is" reduces compilation overhead and yields shorter circuits.
pauliexp isn’t yet documented publicly, but IonQ already supports it. The qiskit‐ionq package already includes helpers for Pauli exponentials (Qiskit‐IonQ helpers, so the hardware/runtime will accept it natively.