Pauli propagation sample
Nobody has claimed this yet.
- Dominant language
- Jupyter Notebook
- Stars
- 499
- Forks
- 102
- PR merge metrics
- No merged PRs in 30d
Description
In the pauli propagation example each gate is executed in a for loop. At the end of the loop the views are swapped for the next iteration (so the 'in' one becomes 'out' and viceversa).
In order to preserve the last 'out' view as the 'out' view, after the for another swap is done: https://github.com/NVIDIA/cuQuantum/blob/4e097de09c9025f3a10a2f574d9fcd95167c1e6d/samples/cupauliprop/kicked_ising_example.cpp#L614
This seems ok so far, but then when computing the expectation value, the 'in' view is used: https://github.com/NVIDIA/cuQuantum/blob/4e097de09c9025f3a10a2f574d9fcd95167c1e6d/samples/cupauliprop/kicked_ising_example.cpp#L631
Shouldn't be that replaced by the 'out' expansion?
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 samples/cupauliprop/kicked_ising_example.cpp, especially the swap after the gate loop near line 614 and the expectation-value calculation near line 631. Trace which view contains the final expansion, then verify the sample computes the expectation value from that view. Run the Pauli propagation example to confirm the result.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- quantum-computing
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100