-
Notifications
You must be signed in to change notification settings - Fork 615
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
Hamiltonian support for Circuit Cutting #4642
Conversation
Hello. You may have forgotten to update the changelog!
|
Codecov ReportAll modified lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## master #4642 +/- ##
=======================================
Coverage 99.63% 99.63%
=======================================
Files 376 376
Lines 33663 33672 +9
=======================================
+ Hits 33539 33548 +9
Misses 124 124
☔ View full report in Codecov by Sentry. |
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.
Awesome work @obliviateandsurrender
I have a few small requests here
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.
Thanks, it looks good! Just a recommendation for the patch
[sc-32504] |
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.
👍
Might be worth updating Issue #3672 . Might actually be closed now.
Context:
qml.cut_circuit
does not work for quantum circuits which computes the expectation values of Hamiltonians with more than one term.Description of the Change: Use
qml.transforms.hamiltonian_expand
to extend support for Hamiltonians.Benefits: Circuit cutting could be used on more realistic circuits.
Possible Drawbacks: The Number of tapes to be computed increases and might give rise to possible overhead in the new scenario.
Related GitHub Issues: #3672