Using the XCC

Development

API

  1. Docs
  2. Walkthrough
  3. Show on GitHub

Walkthrough

Installation

The XCC requires Python version 3.7 or above. Installation of the XCC, as well as all dependencies, can be done using pip:

pip install xanadu-cloud-client

Setup

To use the XCC, a Xanadu Cloud API key (or equivalent JWT refresh token) is required. There are several ways to register your API key with the XCC:

  1. Save your API key to the XCC configuration file using the CLI:

    xcc config set REFRESH_TOKEN "Xanadu Cloud API key goes here"

  2. Set the XANADU_CLOUD_REFRESH_TOKEN environment variable:

    export XANADU_CLOUD_REFRESH_TOKEN="Xanadu Cloud API key goes here"

  3. Save your API key to the XCC configuration file using the Python API:

    import xcc

settings = xcc.Settings(REFRESH_TOKEN="Xanadu Cloud API key goes here")
settings.save()

Afterwards, you can verify that your API key was set correctly using either:

  1. The CLI:

    $ xcc ping
Successfully connected to the Xanadu Cloud.

  2. The Python API:

    import xcc

connection = xcc.Connection.load()
assert connection.ping().ok

Tutorial

The following tutorial illustrates a workflow for submitting a job to the Xanadu Cloud using the CLI. For more detailed usage instructions, use --help or refer to the Python API documentation.

  1. Before submitting a job, it is a good idea to check which devices are currently accepting jobs on the Xanadu Cloud:

    $ xcc device list --status online

    [
    {
        "target": "simulon_gaussian",
        "status": "online"
    },
    {
        "target": "X8_01",
        "status": "online"
    }
]

  2. Suppose that the simulon_gaussian device is of interest. The capabilities, operating conditions, and other properties of a device can be queried by supplying the appropriate flag to the xcc device get command:

    $ xcc device get simulon_gaussian --availability

    {
    "monday": [
        "00:00:00+00:00",
        "23:59:59+00:00"
    ],
    "tuesday": [
        "00:00:00+00:00",
        "23:59:59+00:00"
    ],
    "wednesday": [
        "00:00:00+00:00",
        "23:59:59+00:00"
    ],
    "thursday": [
        "00:00:00+00:00",
        "23:59:59+00:00"
    ],
    "friday": [
        "00:00:00+00:00",
        "23:59:59+00:00"
    ],
    "saturday": [
        "00:00:00+00:00",
        "23:59:59+00:00"
    ],
    "sunday": [
        "00:00:00+00:00",
        "23:59:59+00:00"
    ]
}

    Note: Given that simulon_gaussian is a simulator, it does not have any scheduled downtime for maintenance.

  3. Now, consider a Blackbird script stored in a local file named circuit.xbb:

    $ cat circuit.xbb
name example
version 1.0
target simulon_gaussian (shots=4)

MeasureFock() | [0, 1, 2]

    This circuit can be submitted to the simulon_gaussian device using the xcc job submit command:

    $ xcc job submit --name example \
    --target simulon_gaussian \
    --language "blackbird:1.0" \
    --circuit "$(cat circuit.xbb)"

    {
    "id": "4c043f6d-54c7-4915-bbb8-eb1b99c4d88e",
    "name": "example",
    "status": "open",
    "target": "simulon_gaussian",
    "created_at": "2021-09-24 17:52:00.532938+00:00",
    "finished_at": null,
    "running_time": null
}

    Note: Replace cat foo.xbb with Get-Content foo.xbb -Raw on Windows PowerShell.

  4. The ID of a job can be used to retrieve additional information about that job, including its status and running time. Specifically, the ID can be supplied to the xcc job get command along with an optional flag:

    $ xcc job get 4c043f6d-54c7-4915-bbb8-eb1b99c4d88e --status
complete

    The result of a job can be accessed in a similar way:

    $ xcc job get 4c043f6d-54c7-4915-bbb8-eb1b99c4d88e --result

    {
    "output": [
        "[[0 0 0]\n[0 0 0]\n[0 0 0]\n[0 0 0]]"
    ]
}
Previous
Next