ParallelRange with Sliced Matrix

Open
#162 7 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
38/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Stale
Tech stack
python
Domain
backend, hpc

Research direction

Start by running the provided ParallelRange reproducer with the sliced right[:,:,ii] input and compare it with the standalone matmul that succeeds. Trace the ParallelRange and matmul entry points to find where the slice dimensions are handled; done means the looped matmul completes without failure and produces the expected result shape.

Written by the indexing model from the issue text.

Description

If you slice a matrix in the ParallelRange matmul does not detect the change in dimension and fails:

res = af.constant(0,20,20,1000 )    
left = af.constant(0, 20, 40)
right = af.constant(0, 40,20, 1000)

af.matmul(left, right[:,:,0]) # this works
for ii in af.ParallelRange(10):
            res[:,:,ii] = af.matmul(left, right[:,:,ii]) #will fail
Dominant language
Python
Stars
422
Forks
63
PR merge metrics
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from arrayfire/arrayfire-python

All issues in arrayfire/arrayfire-python

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.