-
Notifications
You must be signed in to change notification settings - Fork 592
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
[Return-types #3] QNode integration, enable and disable functions #2860
Conversation
…yLaneAI/pennylane into refactor_return_shot_vector
… into return_types
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.
@rmoyard great push with this! 💪 🔥
No concrete blocker, just curious about some things.
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.
Looks good! 💪 🥇 Massive push here, great to have all these tests.
I'm wondering about the note on skipping some sampling tests.
The PR became quite big eventually, it could help to separate some conceptual parts (e.g., have backrop be tested in a separate PR) in other such cases.
Co-authored-by: antalszava <antalszava@gmail.com>
…ennylane into return_types_qnode
[sc-24246] |
Context:
Third PR of the new return type project.
Description of the Change:
We add the QNode integration of the new return types.
The changes are made separately from the main pipeline. It can be activated by
qml.enable_return()
, deactivated by
qml.disable_return()
and we can return mode byqml.active_return
.Example
Forward pass:
Backpropagation: