Closed duanyh12 closed 2 years ago
Hi @duanyh12 This is due to the lack of full support for MultiRZ in LightningGPU, as well as the limited shots>0 support in the 0.23 release. If you install the pre-release 0.24 version (soon to be the fully released 0.24 version), this is working as expected for the exact case.
As for the variation expected with the finite-shots>0, let me check.
[[1. 1.]
[1. 1.]]
Lightning Qubit PennyLane plugin
-10.24677464628668
PennyLane plugin for GPU-backed Lightning device using NVIDIA cuQuantum SDK
-10.246774646286685
PennyLane plugin for GPU-backed Lightning device using NVIDIA cuQuantum SDK
-10.246774646286685
PennyLane plugin for GPU-backed Lightning device using NVIDIA cuQuantum SDK
-10.246774646286685
This required a quick fix. v0.24 will have this resolved, and will be released tomorrow.
Confirming the issue is resolved with v0.24. Really appreciate the help!
Expected behavior
For a QAOA max cut problem, here I am comparing the qnode results from 4 different devices:
Code goes:
I would expect
cost1(params_init)
to matchcost2(params_init)
and to roughly matchcost4(params_init)
.cost3(params_init)
should be an integer. Let me know if I am mistaken.Actual behavior
Additional information
No response
Source code
No response
Tracebacks
No response
System information
Existing GitHub issues