Specify QPU Endpoint
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 1.5k
- Forks
- 358
- Avg merge
- 1d 58m
- Merged PRs (30d)
- 4
Description
Issue Description
The QCS API supports engagement with, and job submission to, QPU endpoints. These represent execution on a particular architecture, such as Aspen-9, but there may be multiple such endpoints. Some may serve live access to the quantum processor; others may serve simulated access. There is a system-determined "default" which is used for engagement when no endpoint is specified; however, certain users may prefer to engage with and send jobs to alternate endpoints for testing.
Proposed Solution
Add an endpoint_id optional keyword argument to EngagementManager constructor, which will then create and store engagements for that particular endpoint. This will propagate through the rest of the related classes, which depend on the EngagementManager for the URLs used to connect and run jobs.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the EngagementManager constructor and trace the related classes that use it for connection and job URLs. Confirm how the QCS API represents endpoint-specific engagements, then verify that an optional endpoint_id selects the requested endpoint while preserving the default behavior when it is omitted.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- api, quantum-computing
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100