microsoft / microsoft/azure-quantum-python
Add support for `qir.v1` input data format for cirq Targets
Open
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 160
- Forks
- 113
- Avg merge
- 6d 23h
- Merged PRs (30d)
- 1
Description
Feature Request: It would be great if we could extend the azure.quantum.cirq.targets.Target with a QirTarget (or similar) sub-class that supports the qir.v1 input data format in the same way that the azure.quantum.qiskit.backends.AzureBackendBase is extended by the AzureQirBackend
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 by reading azure.quantum.cirq.targets.Target and compare it with the AzureQirBackend extension of azure.quantum.qiskit.backends.AzureBackendBase. Determine how qir.v1 input is handled there and what equivalent Cirq target behavior is required; done means a Cirq target accepts qir.v1 input in the same way.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- azure, python
- Domain
- cloud
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100