Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Name <--> Device <--> Processor ID <--> Simulator correspondence #2820

Closed
mpharrigan opened this issue Mar 6, 2020 · 2 comments
Closed

Name <--> Device <--> Processor ID <--> Simulator correspondence #2820

mpharrigan opened this issue Mar 6, 2020 · 2 comments
Labels
area/google complexity/medium introduces/modifies 3-5 concepts, takes max up to a month for an advanced contributor kind/feature-request Describes new functionality priority/p2 Next release should contain it triage/accepted there is consensus amongst maintainers that this is a real bug or a reasonable feature to add

Comments

@mpharrigan
Copy link
Collaborator

Currently, there are disjoint pieces of information that should in principle be associated with each other

  • A specific chip/fridge/(cooldown?) combination has a name -- often colloquial -- by which we refer to it.
  • That has a processor_id used to get a QuantumEngine[Sampler] to run jobs
  • processor_id used to get stats
  • There's a Device object that encodes qubits and connectivity
  • Gatesets, Target gateset vs supported gateset #2819
  • You might want a simple noise model (or other simulators) for testing that is roughly tied to the device in question.

It would be nice to have a simple way to treat all these things in one nice bundled blob of data about a "quantum processor" so you can seamlessly use all the information and features available
@mpharrigan mpharrigan mentioned this issue Aug 3, 2020
Closed
@mpharrigan mpharrigan mentioned this issue Aug 11, 2020
Open
@balopat balopat added area/google kind/feature-request Describes new functionality triage/accepted there is consensus amongst maintainers that this is a real bug or a reasonable feature to add complexity/medium introduces/modifies 3-5 concepts, takes max up to a month for an advanced contributor labels Aug 13, 2020
@balopat balopat added the priority/p2 Next release should contain it label Oct 1, 2020
@mpharrigan mpharrigan mentioned this issue Jan 19, 2022
Merged
@95-martin-orion
Copy link
Collaborator

Paging @MichaelBroughton as the latest Device owner.

@mpharrigan
Copy link
Collaborator Author

#4842 is sortof what I was imagining here. I was hoping it would be more of a native part of our type ecosystem rather than sitting on top of Sampler, AbstractProcessor, and Device; but that's where we are

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
area/google complexity/medium introduces/modifies 3-5 concepts, takes max up to a month for an advanced contributor kind/feature-request Describes new functionality priority/p2 Next release should contain it triage/accepted there is consensus amongst maintainers that this is a real bug or a reasonable feature to add
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@balopat @mpharrigan @95-martin-orion