[Capture] Integrate plxpr transforms with execution pipeline #6914
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
mudit2812
changed the title
mudit2812
force-pushed
the
capture-transforms-integration
branch
from
192abd6 to
7eeac8e
Compare
albi3ro
reviewed
Feb 4, 2025
Comment on lines
+572
to
+574
| if not self: | ||
| f = partial(qml.capture.PlxprInterpreter().eval, jaxpr, consts) | ||
| return jax.make_jaxpr(f)(*args) |
There was a problem hiding this comment.
If there's no transforms, do we need to recapture it at all?
There was a problem hiding this comment.
I only added this to adhere to the return type spec (jax.core.ClosedJaxpr). I don't want to change the return type spec because jax.core.ClosedJaxpr carries more info than jax.core.Jaxpr (both jaxpr and consts). I could update it to return tuple[jax.core.Jaxpr, Sequence[Number]], though that seems inconsistent with everything else we currently have.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Before submitting
Please complete the following checklist when submitting a PR:
All new features must include a unit test.
If you've fixed a bug or added code that should be tested, add a test to the
test directory!
All new functions and code must be clearly commented and documented.
If you do make documentation changes, make sure that the docs build and
render correctly by running
make docs.Ensure that the test suite passes, by running
make test.Add a new entry to the
doc/releases/changelog-dev.mdfile, summarizing thechange, and including a link back to the PR.
The PennyLane source code conforms to
PEP8 standards.
We check all of our code against Pylint.
To lint modified files, simply
pip install pylint, and thenrun
pylint pennylane/path/to/file.py.When all the above are checked, delete everything above the dashed
line and fill in the pull request template.
Context:
Description of the Change:
Benefits:
Possible Drawbacks:
Related GitHub Issues:
[sc-83799] [sc-84017]