pymc-devs / pymc-devs/pytensor
Default typify in JITLinkers expects tensors/arrays, why?
Open
Nobody has claimed this yet.
backend compatibility
- Dominant language
- Python
- Stars
- 644
- Forks
- 208
- Avg merge
- 2d 14h
- Merged PRs (30d)
- 16
Description
Description
(And now from copying the approach also the PyTorch Linker)
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the linked lines 22-28 in pytensor/link/jax/dispatch/basic.py, then compare the copied approach in the PyTorch Linker. Determine why the default typify behavior assumes tensors or arrays and what behavior is intended for other inputs. Done means the expected behavior is resolved and the relevant linker implementation is corrected or documented.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python, pytorch
- Domain
- backend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100