-
Notifications
You must be signed in to change notification settings - Fork 621
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
Add qml.workflow.construct_execution_config(qnode)(*args,**kwargs)
#6901
base: master
Are you sure you want to change the base?
Conversation
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## master #6901 +/- ##
=======================================
Coverage 99.59% 99.59%
=======================================
Files 478 479 +1
Lines 45295 45317 +22
=======================================
+ Hits 45113 45135 +22
Misses 182 182 ☔ View full report in Codecov by Sentry. |
Co-authored-by: Christina Lee <[email protected]>
Co-authored-by: Christina Lee <[email protected]>
…nnylane into add-construct-exec-config
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.
❤️ This has made me realize we should set the interface in _resolve_execution_config
, but that can be a follow on.
I have a feeling this is going to be really useful.
Context:
The execution configuration of a particular
QNode
instance is needed in our source code occasionally for various things (such as getting the gradient function).Description of the Change:
This PR introduces a new helper function in the
workflow
module. Specifically,_resolve_execution_config
str
dunder method for prettier printingBenefits: Simplifies some code found in
specs.py
andconstruct_batch.py
.Possible Drawbacks: None.
[sc-83343]