Skip to main content

Interface with Seeqc Cloud

Project description

SEEQC CLI User Guide

Seeqc CLI is a library for interfacing with SEEQC's quantum devices via the cloud.

Prerequisite

SEEQC CLI requires an installation of Python>=3.8 along with Pip. We suggest installing SEEQC CLI into a new virtual environment. Using SEEQC CLI will require a username and password which can be obtained by request.

Installation

The library should be installed from PyPi using Pip as:

 pip install seeqc-client

This will install SEEQC CLI into your active Python environment along with its dependencies.

Getting Started

Instantiate the client as:

from seeqc_client import Client
client = Client()

The client must then be initialised in order to authenticate to the server. The basic initialisation is performed as

client.initialise()

This will prompt username and password entry and upon success provide the client with the credentials required to access our systems. The client will require re-instantiation once per day.

####Programmatic access To facilitate programmatic access the client may be initialised with a path to a refresh token file that contains an authentication token linked to an account:

client.initialise(<token path>)

The token may be generated using the following call that will require manually inputting credentials and will produce a refresh token for this account stored in a file:

client.gen_token(<target token path>)

Running Experiments

Experiments can be created using QASM format files with a subset of QASM commands being accepted:

  • qreg q[<num_qubits>]
  • rx(pi/2)
  • rx(-pi/2)
  • ry(pi/2)
  • ry(-pi/2)
  • rx(<angle>) where <angle> is a floating point number
  • ry(<angle>) where <angle> is a floating point number
  • iswap q[<qubit_a>] q[<qubit_b>]
  • measure

Note that if the iswap instruction is used it is necessary to also provide a definition of the iSWAP gate for the program to be valid in OpenQASM, however this definition will be ignored and the iSWAP gate will be run natively instead.

exp = client.create_experiment('./my_experiment.qasm')

This will create a new experiment object associated with this QASM file that can be submitted to be run as:

exp.run()

This sends the QASM instructions to our platform and returns an experiment id which can be used to recover experiments from another session. The status of the experiment can be checked as:

exp.get_status()

The status will iterate through pending, running and complete. Once the status is set to complete it will automatically retrieve the experiment results, which can then be viewed as:

exp.show_results()

Results here correspond to the population distributions. To return the full quantum register as a numpy array instead use

exp.get_register()

Retrieving Experiments

Metadata on previous experiments can be accessed as:

client.get_experiments(start_index, end_index)

If no indices are provided the last 10 experiments you ran will be returned. From the list of experiments you can retrieve the experiment id which can be used to reload a previous experiment as:

exp = client.get_experiment(experiment_id)

checking the status as shown above will recover the associated data providing the experiment has completed.

Plotting

To produce a histogram of results distributions:

exp.plot()

Running the emulator

The emulator accepts QASM files and the result is returned in the same function call that made the request. The result format is a list of results per shot.

results = client.run_emulator('./my_experiment.qasm')

Project details


Download files

Download the file for your platform. If you're not sure which to choose, learn more about installing packages.

Source Distribution

seeqc-client-0.2.0.tar.gz (118.7 kB view hashes)

Uploaded Source

Built Distribution

seeqc_client-0.2.0-py3-none-any.whl (109.7 kB view hashes)

Uploaded Python 3

Supported by

AWS AWS Cloud computing and Security Sponsor Datadog Datadog Monitoring Fastly Fastly CDN Google Google Download Analytics Microsoft Microsoft PSF Sponsor Pingdom Pingdom Monitoring Sentry Sentry Error logging StatusPage StatusPage Status page