-
Notifications
You must be signed in to change notification settings - Fork 40
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
Implement eval_jaxpr method for lightning.qubit #1002
Conversation
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## master #1002 +/- ##
==========================================
- Coverage 97.13% 91.80% -5.33%
==========================================
Files 228 105 -123
Lines 36786 16496 -20290
==========================================
- Hits 35731 15144 -20587
- Misses 1055 1352 +297 ☔ View full report in Codecov by Sentry. |
…I/pennylane-lightning into lightning-interpreter
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 @albi3ro . I left a couple of non-blocking comments. I didn't notice qnode
present anywhere. Is that deliberate?
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, @albi3ro. We have some failing Cis and format problems. Could you please check this? I left some suggestions for that.
I'm still working on the new execution flow, see PennyLaneAI/pennylane#6596 . So tests for |
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 job! It looks like the failures we have now are essentially linting-related.
@AmintorDusko . Jax was installed, so the tests should have run. Ever seen these warnings before? |
Could you please provide a link to the error or the full traceback? |
https://github.com/PennyLaneAI/pennylane-lightning/actions/runs/12071248436/job/33662775990 |
Thank you as suggested by @maliasadi, this looks like a pytest split problem. |
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!
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 @albi3ro! 🤩
Don't worry about the codecov warnings! This is not related to your PR and your tests have 💯 coverage. We will fix the issue with CoverageWarning: No data was collected. (no-data-collected)
in parallel runs of our pytests as a follow-up.
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 to me
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.
Happy to approve!
Context:
Now that we are decently good at capturing workflows into jaxpr, we want to start natively executing jaxpr.
We recently merged such a feature for
DefaultQubit
(PennyLaneAI/pennylane#6594), and now want to add it tolightning.qubit
as well.Description of the Change:
Implements
LightningQubit.eval_jaxpr
via aLightningInterpreter
class.Benefits:
Execution of captured jaxpr code.
Possible Drawbacks:
Related GitHub Issues:
[sc-72591]