-
Notifications
You must be signed in to change notification settings - Fork 70
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
Advanced indexing #235
Advanced indexing #235
Conversation
Note that, when deciding where to put the extra dimensions in a partial-basic, partial-advanced expression, NumPy considers constants as advanced arrays, so if it sees something like
prints:
|
@manopapad : thank you for finding this bug. I will push the fix shortly |
61e6847
to
acdae9d
Compare
In the case when input arrays (index arrays) are broadcasted and, legate not always will partition them (it will sometimes just broadcast them). This doesn't effect correctness.
8e6b2bb
to
95ae53d
Compare
I have fixed it by basically removing this check. In some cases, when index array is promoted at the front of the array, Legate will decide not to partition it and, instead, broadcast it to all index points. This doesn't change the logic in the task and doesn't effect correctness |
This is ready to merge. Great work! |
Thank you for your help! |
Adding support for advanced indexing