-
Notifications
You must be signed in to change notification settings - Fork 39
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Pass control values to the L-Qubit kernels #576
Conversation
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## master #576 +/- ##
==========================================
+ Coverage 98.95% 99.08% +0.12%
==========================================
Files 167 201 +34
Lines 24382 29290 +4908
==========================================
+ Hits 24128 29021 +4893
- Misses 254 269 +15 ☔ View full report in Codecov by Sentry. |
Support arbitrary controlled values in lightning [sc-51996] |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nice work. Super close to approval! I left some comments.
pennylane_lightning/core/src/simulators/lightning_gpu/StateVectorCudaManaged.hpp
Show resolved
Hide resolved
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thank you for your nice work!
pennylane_lightning/core/src/simulators/lightning_qubit/StateVectorLQubit.hpp
Show resolved
Hide resolved
pennylane_lightning/core/src/simulators/lightning_qubit/StateVectorLQubit.hpp
Outdated
Show resolved
Hide resolved
Nice job @vincentmr ! Happy to approve. A kind reminder: please make sure all CI checks passed before merge. |
Before submitting
Please complete the following checklist when submitting a PR:
All new features must include a unit test.
If you've fixed a bug or added code that should be tested, add a test to the
tests
directory!All new functions and code must be clearly commented and documented.
If you do make documentation changes, make sure that the docs build and
render correctly by running
make docs
.Ensure that the test suite passes, by running
make test
.Add a new entry to the
.github/CHANGELOG.md
file, summarizing thechange, and including a link back to the PR.
Ensure that code is properly formatted by running
make format
.When all the above are checked, delete everything above the dashed
line and fill in the pull request template.
Context:
Following up on #516 , this PR introduces
controlled_values
everywhere to improve the flexibility of the n-control interface.Description of the Change:
Pass
controlled_values
around everywherecontrolled_wires
are to be found. I also remove theextern
definitions fromGateImplementationsLM.hpp
(not effect on build times AFAIK).Benefits:
Simpler decompositions for non-strictly
1
-controlled gates (improved perf). For example, this is important in Grover's algorithm. While it makes no difference when searching for the111...111
string (best case scenario), it makes a significant difference (~50%) when searching for the000...000
string (worst case scenario). These are extreme cases, but it gives an idea. Here are some benchmarks performed on a single Perlmutter core before and after this PR.The
extern
definitions need not be maintained.Possible Drawbacks:
Increased code complexity.
Related GitHub Issues: