You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Right now, qbraid.devices of the device_layer branch contains folders assigned to each qbraid supported circuit-building package. Each circuit-building package is linked to one or more QPU and/or simulator provider(s). Eventually, we will have a get_devices function local to each circuit-building package folder so that this global get_devices function can simply call on each, but for now, it will suffice to have all the functionality contained in this one function (we can easily break it up later). The ultimate goal of this issue is to arrive at an implementation of get_devices that pulls supported device lists directly from each qbraid supported provider. The steps toward this goal are as follows:
Fill in the "Available Devices" table of Device_Layer_Docs.ipynb with all of the devices and simulators accessible through braket, cirq, and qiskit (this will require some digging). There are a few listed already as examples, but with some missing information. The following links were the starting point to what exists so far: Amazon Braket supported devices, Google devices, BasicAer: Python-based Simulators.
Hard-code get_devices using the completed "Available Devices" table so that we have a working version.
Fill in the "Functions to get available devices" table directly underneath. This table should include any existing built-in functions that return lists or dicts of available devices or simulators. For example, qiskit has a backends function that returns a list of backends matching specified filtering. Some packages may not have any such functions, while others may have more than one.
Re-implement get_devices so that it leverages any useful updates to the architecture of the devices folder e.g. divide and conquer with local/global versions as described above. Incorporate the "device getter functions" found in Step 3 wherever possible to eliminate hard-coding.
The text was updated successfully, but these errors were encountered:
Right now,
qbraid.devices
of the device_layer branch contains folders assigned to each qbraid supported circuit-building package. Each circuit-building package is linked to one or more QPU and/or simulator provider(s). Eventually, we will have aget_devices
function local to each circuit-building package folder so that this globalget_devices
function can simply call on each, but for now, it will suffice to have all the functionality contained in this one function (we can easily break it up later). The ultimate goal of this issue is to arrive at an implementation ofget_devices
that pulls supported device lists directly from each qbraid supported provider. The steps toward this goal are as follows:get_devices
using the completed "Available Devices" table so that we have a working version.backends
function that returns a list of backends matching specified filtering. Some packages may not have any such functions, while others may have more than one.get_devices
so that it leverages any useful updates to the architecture of the devices folder e.g. divide and conquer with local/global versions as described above. Incorporate the "device getter functions" found in Step 3 wherever possible to eliminate hard-coding.The text was updated successfully, but these errors were encountered: