Stable PyMC-to-numba API?
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 207
- Forks
- 28
- Avg merge
- 7d 21h
- Merged PRs (30d)
- 1
Description
Hi all --
@bob-carpenter and I recently released 0.0.1 of walnutpie, which takes a lot of inspiration from this package and @aseyboldt's work on nuts-rs.
In particular, with an eye for compatibility, I modeled our callback type on the one nuts-rs uses. I'd love to allow users to efficiently plug in pymc models using numba like is done here, but it seems like it depends a lot on pymc internals.
Is there any chance that this kind of API could be exposed (either by nutpie or pymc itself) in a stable way we could depend on in other packages?
Contributor guide
No contributing guide indexed for this repository
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 by reviewing the callback type linked from walnutpie and the existing PyMC-to-numba integration, especially the PyMC internals it currently depends on. Done would be a decided, stable API exposed by nutpie or PyMC that other packages can depend on, along with agreement on its compatibility boundary.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- api
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100