-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
update parallel XEB methods to support circuits instead of single gates #6940
base: main
Are you sure you want to change the base?
Conversation
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #6940 +/- ##
=======================================
Coverage 97.86% 97.86%
=======================================
Files 1084 1084
Lines 94408 94447 +39
=======================================
+ Hits 92393 92432 +39
Misses 2015 2015 ☔ View full report in Codecov by Sentry. |
@@ -403,6 +403,7 @@ def parallel_xeb_workflow( | |||
pool: Optional['multiprocessing.pool.Pool'] = None, | |||
batch_size: int = 9, | |||
tags: Sequence[Any] = (), | |||
entangling_circuit_or_op: Optional[Union['cirq.AbstractCircuit', 'cirq.Operation']] = None, |
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.
Actually, in order to do parallel XEB, we will want to be able to input something like a set of circuits (that each act on two qubits) or a dictionary from pairs to circuits because, for example, we may have different z-phase corrections on different pairs of qubits.
Parallel XEB methods assume they run on specific gate objects ... however some operations need to be represented using a circuit
to run XEB on a circuit call the desired method with
entangling_circuit_or_op=...