Skip to content

How to see which processor has which gateset #4279

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

Closed
balopat opened this issue Jul 1, 2021 · 3 comments
Closed

How to see which processor has which gateset #4279

balopat opened this issue Jul 1, 2021 · 3 comments

Comments

@balopat
Copy link
Contributor

balopat commented Jul 1, 2021

Is your feature request related to a use case or problem? Please describe.

It would be great if the processor would "know" what gateset it accepts - instead of having to pass that in. I find this rather odd. While there is a way to list processors using the Engine API or the UI, there is no way to tell what gate set a processor accepts. The processor.get_device() method takes a list of gate sets which then it uses to validate operations.

processor = engine.get_processor('rainbow')
# Print the device showing qubit connectivity for the Sycamore gateset.
device = processor.get_device([cg.SYC_GATESET])

Describe the solution you'd like

Instead it would be great if a gate set could be determined based on a processor ID.

Describe alternatives/workarounds you've considered

Alternative is to ask someone, use documentation/datasheets (if available).

What is the urgency from your perspective for this issue? Is it blocking important work?
P3 - I'm not really blocked by it, it is an idea I'd like to discuss / suggestion based on principle

@wcourtney
Copy link
Collaborator

processor = engine.get_processor('weber')
spec = p.get_device_specification()
for g in spec.valid_gate_sets:
  print(g.name)

@dstrain115
Copy link
Collaborator

@verult I think this can be closed as part of the device spec work.

@verult
Copy link
Collaborator

verult commented Apr 5, 2022

Yep, closing in favor of #5050

@verult verult closed this as completed Apr 5, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants