PennyLaneAI / PennyLaneAI/catalyst
[Frontend] The lack of a device specific decomposition logic
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 234
- Forks
- 84
- Avg merge
- 2d 15h
- Merged PRs (30d)
- 66
Description
We currently serve all backend devices in a way that they all support an identical set of quantum gates. This design assumption would lead to the failure of decomposition rules for the OpenQasm3/Braket device. We may need to implement a device specific decomposition logic for every supported backend devices in the frontend to properly tackle this issue.
Check the test_unsupported_gate_braket test unit in test_aws_braket_devices.py for an example.
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 test_unsupported_gate_braket test in frontend/test/pytest/test_aws_braket_devices.py to understand the demonstrated failure. Then trace the frontend decomposition handling for supported backend devices. Done means decomposition rules no longer assume identical gate support and work correctly for the OpenQasm3/Braket device and other supported backends.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- compilers
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100