Skip to content
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

Two-qubit RB for QM #985

Draft
wants to merge 15 commits into
base: qua
Choose a base branch
from
Draft

Two-qubit RB for QM #985

wants to merge 15 commits into from

Conversation

stavros11
Copy link
Member

@stavros11 stavros11 commented Sep 23, 2024

Same as #959 but two qubits. As in the other PR this is an almost exact copy of the corresponding qua-libs example. The code here is significantly more complicated and unlike the single-qubit case I have minimal understanding of the implementation. I did the minimal changes required to use this easily with our platforms.

Here is an example action runcard:

platform: qw11q

targets: [["D2", "D1"]]

actions:

- id: Two Qubit RB QUA
  operation: rb_qua_two_qubit
  parameters:
    circuit_depths: [1, 2, 3, 4, 5]
    num_circuits_per_depth: 2
    num_shots_per_circuit: 1000

Those who are interested in using this, note the following:

  1. I think a specific configuration of QM libraries (and Cirq!) is needed for this to work with our cluster, in particular:
cirq                            1.2.0
qm-octave                       2.0.1
qm-qua                          1.1.6
qualang-tools                   0.16.0

It may work with other versions, but I was getting some errors. In particular our cluster needs qm-qua 1.1.6, but I believe this comes with an earlier version of qualang-tools, which causes this code to fail, so I needed to upgrade qualang-tools to a working version and then downgrade qm-qua to 1.1.6.

  1. It will only apply the flux pulse on the high frequency qubit of the CZ and the virtual phases on the two qubits. Other pulses (eg. for parking) included in the CZ sequence will be ignored. This is probably easy to fix though.

Here are some example reports on D1-D2 pair:
http://login.qrccluster.com:9000/8gRCwEV0TMm_r7gkh9PDbg==
http://login.qrccluster.com:9000/cqVHgb85Sb6YrNzCSTXp6A==
Unfortunately, I am not sure yet if the low fidelity is caused by miscalibration or there is a bug somewhere.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
do not merge Soft warning to avoid merging a PR for reason provided in the PR
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant