[braket] Reorder global register to be in original qubit allocation order
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 1.1k
- Forks
- 456
- Avg merge
- 1d 22h
- Merged PRs (30d)
- 165
Description
Required prerequisites
- Consult the security policy. If reporting a security vulnerability, do not report the bug using this form. Use the process described in the policy to report the issue.
- Make sure you've read the documentation. Your issue may be addressed there.
- Search the issue tracker to verify that this hasn't already been reported. +1 or comment there if it has.
- If possible, make a PR with a failing test to give us a starting point to work on!
Describe the bug
Reorder global register to be in original qubit allocation order for braket backend, if we run any qubit mapping.
See comment https://github.com/NVIDIA/cuda-quantum/pull/2416#discussion_r1859550376
See https://github.com/NVIDIA/cuda-quantum/pull/2328 for a similar issue on Anyon
Steps to reproduce the bug
Reorder global register to be in original qubit allocation order for braket backend, if we run any qubit mapping.
See comment https://github.com/NVIDIA/cuda-quantum/pull/2416#discussion_r1859550376
See https://github.com/NVIDIA/cuda-quantum/pull/2328 for a similar issue on Anyon
Expected behavior
qubits are ordered in the original order
Is this a regression? If it is, put the last known working version (or commit) here.
Not a regression
Environment
- CUDA-Q version:
- Python version:
- C++ compiler:
- Operating system:
Suggestions
No response
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 reviewing the Braket backend behavior around qubit mapping and the discussion in PR #2416, then compare the similar Anyon issue in PR #2328. Confirm how the global register is produced; done means mapped qubits are emitted in their original allocation order, with coverage for the reported case.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- backend, quantum-computing
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 28/100