patrick-kidger / patrick-kidger/diffrax
Difference between SaveAt(ts=...) and evaluating with SaveAt(dense=True)
Open
Nobody has claimed this yet.
question
- Dominant language
- Python
- Stars
- 2.1k
- Forks
- 189
- Avg merge
- 3d 18h
- Merged PRs (30d)
- 1
Description
I wonder if there is a difference (in accuracy or performance) between specifying ts during evaluation and evaluating a dense output at these ts afterwards. The result seems to be similar based on my quick experiments, but I assume there might be some differences in more subtle cases?
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 SaveAt(ts=...) and SaveAt(dense=True) entry points and compare their documented evaluation semantics. Investigate whether accuracy, performance, or subtle cases differ, using focused experiments if needed. Done means documenting a clear comparison and the cases where one approach should be preferred.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- backend-api-design
- Issue type
- Documentation
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100