rigetti / rigetti/pyquil

Gate times are not exposed in the device specs API

Open
#503 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Python
Stars
1.5k
Forks
358
Avg merge
1d 58m
Merged PRs (30d)
4

Description

The device.specs object provides the T1/T2 times for each gate:

>>> import pyquil
>>> device = pyquil.api.get_devices(as_dict=True)['8Q-Agave']
>>> device.specs.T1s()
{0: 1.07e-05, 1: 1e-05, 2: 1.55e-05, 3: 1.42e-05, 4: 1.46e-05, 5: 1.49e-05, 6: 1.42e-05, 7: 1.32e-05}
>>> device.specs.T2s()
{0: 1.06e-05, 1: 9.2e-06, 2: 1.25e-05, 3: 1.85e-05, 4: 2.62e-05, 5: 1.28e-05, 6: 1.29e-05, 7: 1.77e-05}

however, the actual gate times are not exposed in the API.

As such, there is no way of accurately using that information to compute the circuit depths (other than using the estimated ballpark values of 50 ns for 1-qubit gates and 150 ns 2-qubit gates).

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start at the device.specs API returned by pyquil.api.get_devices(as_dict=True), alongside the existing T1s() and T2s() entry points. Trace how device specifications are represented and identify where gate timing data should be exposed. Done means callers can retrieve the actual one- and two-qubit gate times through the device specs API.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
api
Issue type
Feature
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.