rigetti / rigetti/qcs-sdk-rust
Python: retrieve_results should return a more ergonomic data structure
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 15
- Forks
- 4
- Avg merge
- 1h 9m
- Merged PRs (30d)
- 1
Description
Pythons retrieve_results should return a more ergonomic data structure. It currently maps to ExecutionResults which is a trimmed down version of the controller service response. However, it's API requires manual composure of result data and is overall just a less ergonomic version of QPUResultData. We should return that instead.
Contributor guide
No contributing guide indexed for this repository
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 by locating the Python retrieve_results implementation and reading the definitions of ExecutionResults and QPUResultData. Trace the existing result conversion and any related tests; the work is done when retrieve_results returns QPUResultData with the expected result data and the affected tests pass.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python, rust
- Domain
- api, backend-api-design
- Issue type
- Refactor
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100