Setup

First, import the necessary modules from QGL. This will also import numpy into the namespace as np.

The AWGDir environment variable is used to indicate where QGL will store it's output sequence files. First we load the QGL module. It defaults to a temporary directory as provided by Python's tempfile module.

Next we instantiate the channel library. By default bbndb will use an sqlite database at the location specified by the BBN_DB environment variabe, but we override this behavior below in order to use a specific filename. Also shown (but commented out) is the syntax for creating a temporary in-memory database for testing purposes.

The channel library has a number of convenience functions defined to create instruments and qubits, as well as functions to define the relationships between them. Let us create a qubit first:

In order to compile the QGL program into pulse sequences, we need to define a minimal hardware configuration. Basically, we need to specify AWG resources for output pulse compilation and digitizer resources for signal measurement.

Commit the changes to the channel library.

Basic sequence construction and plotting

You can construct simple gate sequences by creating Lists of Pulse objects. These can be constructed by calling various primitives defined for qubits, for example, 90 and 180 degree rotations about X and Y:

This sequence of pulses can be plotted for visual review. First, you must compile the QGL into pulses based on the hardware defined above. Since our Qubit object is a quadrature channel, you see two colors corresponding to the I and Q control signals.

Now, let's plot the second sequence.

Constructing more sophisticated sequences

To get rotations of arbitrary angle (i.e., amplitude control of the pulse), you can use the "theta" primitive:

To rotate about an arbitrary axis, use the "U" primitives:

Z rotations are performed in "software:" they act as frame changes on the following pulses.

Sequences can act on multiple qubits, i.e., channels. Let's create another "logical" qubit channel as well as a "physical" channel.

When you plot a sequence with multiple logical channels, each channel (both I and Q) is plotted seperately.

One can express simultaneous operations with the * operator (meant to evoke a tensor product). If no operation is specified for a channel in a given time slot, an identity (no-op) operation is inserted.

Constructing sequences with measurements

Measurement pulses can be created with the MEAS primitive. Given a qubit X, the compiler finds the associated logical measurement channel and creates a Pulse on that channel. Note that a Trigger pulse for the digitizer is created along with the qubit measurement pulse.

Remember, measurement channel was defined above with:
Qubit q1 is measured by AWG aps2_2 and digitizer dig_1
cl.set_measure(q1, aps2_2, dig_1.ch(1))

Single-sideband modulation

In order to prevent leakage at the source frequency, typically single-sideband (SSB) modulation with IQ mixers is used to generate both control and measurement pulses.

For control pulses, we define the SSB frequency as q1.frequency. In the following example, you can set that parameter to a non-zero SSB to modulate the pulse envelope.

For measurement pulses, we define the SSB frequency as

q1.measure_chan.autodyne_freq

Note that autodyne_freq is different from frequency. In the first case, the SSB frequency is baked directly in the pulse waveform, and is independent of the time when the pulse is applied. In the second case (normally used for the control SSB, see above), the actual pulse shape depends on the time when the pulse occurs. This is in order to maintain the phase reference allowing for arbitrary rotations around any transversal axis.

Longer sequences using list comprehensions

Rabi amplitude

Note the increasing amplitude with each sequence.

T1

Note the delay between the X pulse and the measurement.

Ramsey

Note the varying delay between the X pulses prior to measurement.