-
Notifications
You must be signed in to change notification settings - Fork 6
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
Cross Resonance Routine #821
Comments
Thanks @sorewachigauyo for raising this. It is also needed for the upcoming batch of TII's 2q chips. |
I've added a version using sequences in 8597df3, @andrea-pasquale could you check if that code makes sense? Even using the for-loop variation I cannot see much happening in these qubits These are the qubits being used to run this test: "0": {
"RX": {"duration": 80,"amplitude": 0.3745,"shape": "Gaussian(5)",
"frequency": 5312263656,"relative_start": 0,"phase": 0,"type": "qd"},
"MZ": {
"duration": 2000,"amplitude": 0.15,"shape": "Rectangular()",
"frequency": 6910930000,"relative_start": 0,"phase": 0,"type": "ro"
}
},
"1": {
"RX": {"duration": 80,"amplitude": 0.5448,"shape": "Gaussian(5)",
"frequency": 5393450614,"relative_start": 0,"phase": 0,"type": "qd"},
"MZ": {
"duration": 2000,"amplitude": 0.1,"shape": "Rectangular()",
"frequency": 7.02001e+09,"relative_start": 0,"phase": 0,"type": "ro"
}
}, |
Hi @jevillegasd, If its not too sensitive, could you give some more information about the qubit system you are using? Given that the qubits are 80MHz apart, it is strange that you do not see an effect or even crosstalk-driven Rabi oscillations. We can take it to emails if needed. Maybe you need more power either with an amplifier or higher amplitude. |
Absolutly the QPU is a three qubit chip with fixed frequency qubits coupled together in a straight line (you can see the platform here qiboteam/qibolab_platforms_qrc@77b7b32). The chip has an additional witness qubit and a resonator. Here I list the most relevant parameters.
|
Have you tried to run a cross resonance chevron ? |
The qubits are coupled directly or by bus resonator? Do you have an estimate of the coupling strength from designed values or measured by a two-qubit simultaneous on-resonance Ramsey? |
I still need to make the version with sequences for that as well so that I can use it with QBlox. |
They are directly coupled with a transmission line with a coupling capacitance of 0.5 fF at each transmon, this is about 10 MHz by design. We have not tried to extract this value using simultaneous Ramsey tests, could you explain how can we get this? |
If @sorewachigauyo is referring to the ZZ coupling, there is a PR where we have a draft for that protocol #970. |
Yeah, #970 should help you determine the coupling strength and check if the qubits are coupled or not. Based on the coherence times you measured, you should observe the Ramsey oscillations within the coherence. |
To implement a basic routine for the calibration of cross-resonance (CR) gates.
This involves sending a pulse on the control qubit with the frequency of the target qubit. We vary the pulse length to observe a Rabi oscillation. Based on the state of the control qubit, there will be a splitting of the Rabi frequencies, and we can select a pulse length$t$ such that the phase difference between the two oscillations is $\pi$ . This then implements a CNOT gate.
A basic CR calibration is as follows:
The frequency of each Rabi oscillation is proportional to the amplitude of
cr_pulse
, so to obtain an optimal parameter for the amplitude, a 2D chevron of CR pulse amplitude and length can be performed.By also simultaneously driving the target qubit on resonance, an approximate interaction forms
$A_{CR} (\omega_{ZX} ZX + \omega_{IX} IX) + A_t \omega_{R2} IX $ $A_{CR}$ is the amplitude of $\omega_{ZX}, \omega_{IX}$ is determined by the target qubit Rabi frequency $\omega_{R2}$ , effective qubit-qubit coupling, detunings and anharmonicites and $A_t$ is the amplitude of the second drive.
where
cr_pulse
,A basic experiment with the second drive is as follows:
The text was updated successfully, but these errors were encountered: