patrick-kidger / patrick-kidger/diffrax
Add differentiable event handling
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 2.1k
- Forks
- 189
- Avg merge
- 3d 18h
- Merged PRs (30d)
- 1
Description
One thing that needs thinking about is how this compares to the use of jump processes as a driving control, which morally speaking do something very similar.
- Discrete terminating events
- Discrete non-terminating events
- Continuous terminating events
- Continuous non-terminating events
The continuous events can be implemented by using the most recent dense_info and performing a nonlinear solve to locate the event location.
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 by reviewing the existing discrete terminating-event implementation and how the most recent dense_info is exposed; the issue names no file or test. Compare the completed case with the three unchecked combinations, using a nonlinear solve to locate continuous event positions. Done means the remaining event types are implemented and their relationship to jump processes is clarified.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- machine-learning
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 20/100