Conversation
3ce54c7 to
92f61ed
Compare
92f61ed to
a6cb68d
Compare
546100c to
4b02064
Compare
There was a problem hiding this comment.
This is looking pretty good.
Mostly I want to believe there is still room to simplify things / reuse code.
This is also a good opportunity to simplify the idx_list. There's no reason to use ScalarTypes in the dummy slices, and it's complicating our equality and hashing.
What about using simple integers to indicate what is the role of each index variable?
old_idx_list = (ps.int64, slice(ps.int64, None, None), ps.int64, slice(ps.int64, None, ps.int64))
new_idx_list = (0, slice(1, None, None), 2, slice(3, None, 4))Having the indices could probably come in handy anyway. With this we shouldn't need a custom hash / eq, we can just use the default one from __props__.
| else: | ||
| x, y, *idxs = node.inputs | ||
| x, y = node.inputs[0], node.inputs[1] | ||
| tensor_inputs = node.inputs[2:] |
There was a problem hiding this comment.
I don't like the name tensor_inputs, x, y are also tensor and inputs. Use index_variables?
There was a problem hiding this comment.
Still using tensor_inputs in the last code you pushed
| # must already be raveled in the original graph, so we don't need to do anything to it | ||
| new_out = node.op(raveled_x, y, *new_idxs) | ||
| # But we must reshape the output to math the original shape | ||
| new_out = AdvancedIncSubtensor( |
There was a problem hiding this comment.
You should use type(op) so that subclasses are respected. It may also make sense to add a method to these indexing Ops like op.with_new_indices() that clones itself with a new idx_list. Maybe that will be the one that handles creating the new idx_list, instead of having to be here in the rewrite.
There was a problem hiding this comment.
Currently functions ravel_multidimensional_bool_idx and ravel_multidimensional_bool_idx don't assume the subclass in the same way, but it'd be nice if you could check. Also, if I am giving up on some rewrites too quickly here, please let me know.
pytensor/tensor/subtensor.py
Outdated
| def __init__(self, idx_list): | ||
| """ | ||
| Initialize AdvancedSubtensor with index list. | ||
|
|
||
| Parameters | ||
| ---------- | ||
| idx_list : tuple | ||
| List of indices where slices are stored as-is, | ||
| and numerical indices are replaced by their types. | ||
| """ | ||
| self.idx_list = tuple( | ||
| index_vars_to_types(idx, allow_advanced=True) for idx in idx_list | ||
| ) | ||
| # Store expected number of tensor inputs for validation | ||
| self.expected_inputs_len = len( | ||
| get_slice_elements(self.idx_list, lambda entry: isinstance(entry, Type)) | ||
| ) | ||
|
|
||
| def __hash__(self): | ||
| msg = [] | ||
| for entry in self.idx_list: | ||
| if isinstance(entry, slice): | ||
| msg += [(entry.start, entry.stop, entry.step)] | ||
| else: | ||
| msg += [entry] | ||
|
|
||
| idx_list = tuple(msg) | ||
| return hash((type(self), idx_list)) |
There was a problem hiding this comment.
This already exists in Subtensor? If so create a BaseSubtensor class that handles idx_list and hash/equality based on it.
Make all Subtensor operations inherit from it
There was a problem hiding this comment.
Note this advice may make no sense if we simplify the idx_list to not need custom hash / eq
There was a problem hiding this comment.
hash is a bit different based on whether it is *IncSubtensor or not in the current implementation. Wrote about the Python 3.11 slice not being hashable below.
pytensor/tensor/subtensor.py
Outdated
| ) | ||
| else: | ||
| return vectorize_node_fallback(op, node, batch_x, *batch_idxs) | ||
| # With the new interface, all inputs are tensors, so Blockwise can handle them |
There was a problem hiding this comment.
Comment should not mention a specific time period. Previous status is not relevant here
There was a problem hiding this comment.
Also we still want to avoid Blockwise eagerly if we can
There was a problem hiding this comment.
All time periods should be removed from comments that were added in this PR.
pytensor/tensor/variable.py
Outdated
| pattern.append("x") | ||
| new_args.append(slice(None)) | ||
| else: | ||
| # Check for boolean index which consumes multiple dimensions |
There was a problem hiding this comment.
This is probably right, but why does it matter that boolean indexing consumes multiple dimensions? Aren't we doing expand_dims where there was None -> replace new_axis by None slice -> index again?
There was a problem hiding this comment.
There might be a more dynamic approach, but I have had trouble with multidimensional bool arrays and ellipsis, e.g. x[multi_dim_bool_tensor,None,...] will not know where to add the new axis.
|
Just wanted to repeat, this is looking great. Thanks so far @jaanerik I'm being picky because indexing is a pretty fundamental operation, so want to make sure we get it right this time. |
@ricardoV94 I am struggling a bit with understanding your example, because old_idx_list also has ints. Could you clarify how you see constant index and variable index both working here. If you have the last slice of Absolutely no problem with being picky. I am very grateful for the feedback :) |
|
I updated it, it was some copy-paste typos. Old_idx doesn't have ints, only |
4787bc9 to
5ba887b
Compare
d821794 to
02a8d24
Compare
c84885b to
e127e4b
Compare
Refactored to use Removed many comments, removed most makeslice, slicetype usage, but refactoring |
0b51466 to
13d025a
Compare
|
Let's try not to touch XTensor if we can, to keep this PR moving along. If it's using SliceTypes let it remain for those |
| elif len(shape_parts) == 1: | ||
| shape = shape_parts[0] |
There was a problem hiding this comment.
Is this a bug fix? If so can we add a regression test?
There was a problem hiding this comment.
Added test_transform_take_scalar_index() in tests/tensor/rewriting/test_subtensor.py. A bug fix for the case where all shape_parts are empty tuples (e.g., scalar index on 1D array).
ricardoV94
left a comment
There was a problem hiding this comment.
This is looking nearly done!
I saw you did some changes to xtensor. You mentioned that was growing out of scope so I didn't review. Let me know how you want to proceed there, or if you need guidance.
I flagged some changes that seem to be a conflict from main mis-resolved?
Otherwise it's really shaping up!!!
f4b4b8c to
4ec9707
Compare
|
I currently simply reverted the xtensor refactor assuming it's okay to be labelled as out of scope for this PR. There was a very small refactor for xtensor that needed to stay in. Thanks for your help. Asking you for another review : ) @ricardoV94 |
ricardoV94
left a comment
There was a problem hiding this comment.
This is pretty much done. Just some small nits / suggestions. I'll try to take care of them this week if you don't get to them before
pytensor/tensor/subtensor.py
Outdated
| """ | ||
| counter = [0] | ||
| self.idx_list = tuple( | ||
| index_vars_to_positions(entry, counter, allow_advanced=allow_advanced) |
There was a problem hiding this comment.
I don't think this should be done by the Op. Just make it receive the correct idx_list and maybe validate it. The allow_advanced at the base op also seems suspect
There was a problem hiding this comment.
Tried to refactor it, but please take a look.
657f308 to
64c08a5
Compare
There was a problem hiding this comment.
Did a full review at last.
Pushing back against one of the helpers that seems to be doing way too much (tbf it was already a mess before this PR), and a bunch of new tests / test changes.
Every single new test that was supposed to be a bug regression (that I tested) seems to pass just fine in main, which makes me suspect that it's regression against intermediate breaking changes from previous iterations. I would revert those.
|
@jaanerik, somewhat unrelated, would you like to join our internal dev discord? This contribution is pretty massive so you definitely earned a ticket |
I joined a pymc discord. Is that the one you meant? Wrote to #chat |
64c08a5 to
c546c55
Compare
ricardoV94
left a comment
There was a problem hiding this comment.
1 suggestion, 1 nit, and 3 places I noted a wrong rebase from main.
I think this is the final round at last :)
96b5945 to
b0bdf68
Compare
|
Rebased (vectorize_node in xtensor was there before rebase as well, but due to a git conflict I added it back later). Also scan/rewriting was refactored because some numba and jax tests were failing. |
b0bdf68 to
528d91e
Compare
|
@jaanerik I cleaned a few more things, squashed all commits and force pushed. I removed the new |
528d91e to
8c6052b
Compare
- newaxis is handled as explicit DimShuffel on the inputs - slices are encoded internally, so the Ops only take numerical inputs Co-authored-by: Ricardo Vieira <28983449+ricardov94@users.noreply.github.com>
8c6052b to
9016175
Compare
Description
Allows vectorizing AdvancedSetSubtensor.
Gemini picks up where Copilot left off.
Related Issue
Checklist
Type of change