Build a stripped down version of the sampler/solver to see what is reducing our performance if anything
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 13
- Forks
- 3
- Avg merge
- 19h 43m
- Merged PRs (30d)
- 1
Description
build a really stripped down version of our infrastructure. No classes, just the sampler, parameters, and ODEs / diffrax solve. To see if there are dramatic improvements to the performance of fitting.
If so, slowly add back onto the model until we understand what exactly is slowing it down and how to best avoid it.
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 locating the sampler, parameters, ODEs, and Diffrax solve used by the fitting workflow. Compare the stripped-down implementation's performance with the existing infrastructure, then add components back incrementally until the source of the slowdown is identified and documented.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- performance
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100