-
Notifications
You must be signed in to change notification settings - Fork 175
ENH: Support dynamic slice indexing in JAX backend via lax.dynamic_slice #1905
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
Open
ayulockedin
wants to merge
1
commit into
pymc-devs:main
Choose a base branch
from
ayulockedin:subtensor-fix
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
+159
−1
Open
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or 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
This file contains hidden or 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
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.
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 is not statically provable, because i may be less than 3 units away from the edge
Uh oh!
There was an error while loading. Please reload this page.
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.
@ricardoV94 You are absolutely right. In pure NumPy semantics, the slice truncates near the edge, so the output length isn't strictly guaranteed.
However, XLA strictly requires static shapes and cannot compile dynamically sized outputs. To work around this, jax.lax.dynamic_slice intentionally deviates from NumPy by clipping out-of-bounds indices to guarantee the requested static size.
For the Scalable Online SSM project (and most sliding-window algorithms in pymc-extras), the models structurally guarantee that i stays within bounds, so we wouldn't actually hit this edge case in practice.
Since strictly enforcing NumPy's truncating semantics means dynamic slices with Tracers can never compile in JAX, would it be acceptable to adopt JAX's clipping behavior here as a pragmatic trade-off? If you would prefer a different architectural approach for handling dynamic sliding windows in JAX, I am completely open to pivoting.
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.
@ricardoV94 If we want to maintain strict NumPy compliance, I could investigate, but that might significantly complicate the JAX JIT graph. What do you think is the best path forward?