-
Notifications
You must be signed in to change notification settings - Fork 139
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Dynamic support of QPU topologies for the mapping pass #1589
Comments
To illustrate this. The OQC SDK or the from client.qcaas_client.client import OQCClient, QPUTask
# email =
# password =
def get_two_qubit_coupling(email: str, password: str) -> list:
client = OQCClient(url='https://int.cloud.oqc.app/qpu',
email=email,
password=password)
qpu_id = "qpu:uk:3:9829a5504g"
calibration = client.get_calibration(qpu_id)
# fetched from https://int.uk.cloud.oqc.app/9829a5504g/monitoring/calibrations
return list(calibration['two_qubit'].keys())
get_two_qubit_coupling(email, password) Return
Shows unique couplings between different coupling similar to the static definitions here note the 1-based indexing in the above as opposed to the better zero based indexing in the cudaq routing file. Since this is authentication protected here's a portion of the returned JSON to work against which could be included from this fake server utility as a new response
|
What about using fCX to disconnect where we may have sporadic low fidelities (None, 0 or < some threshold)? |
From the IQM side — we've recently added the possibility to specify gates per pair/qubit and in the near future we plan to make the would architecture endpoint /quantum-architecture calibration-aware. |
Another comment from IQM side — in addition to what @kukushechkin said above, we also plan, in near future, to incorporate fidelity data into quantum architecture, explicitly list gate implementations, and separate QPU topology data from "gates". So, overall, it should be possible to fetch:
It may look something like this:
and
|
Just for clarification, this item is still available for anybody to grab and implement for UnityHack. |
Required prerequisites
Describe the feature
CUDA-Q currently supports specification of QPU mapping topologies via static configuration files in
It would be nicer if these topologies could be dynamically fetched from their corresponding host services, either via a standalone command-line tool and/or a library call that could be integrated into the runtime. (The most ideal solution is a common implementation that supports both options.)
The text was updated successfully, but these errors were encountered: