use `diffrax.diffeqsolve(throw=False)` to delay raising integration related errors.
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 13
- Forks
- 3
- Avg merge
- 19h 43m
- Merged PRs (30d)
- 1
Description
rather than diffrax.diffeqsolve raising an error directly, lets give the user the ability to log the particular parameters that caused an error somewhere else before raising and stopping execution.
This will likely require some sort of parameters optionally passed to simulate util helper that save the particular parameters that caused the error.
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
Trace the simulate utility and its current diffrax.diffeqsolve call to understand how integration errors are raised. Define the error-handling path so the parameters causing a failure can be retained or logged before execution stops, and verify that the delayed-raising behavior works as intended.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100