SciML / SciML/JumpProcesses.jl
allow reset_aggregated_jumps! to update without reinitializating
Nobody has claimed this yet.
- Dominant language
- Julia
- Stars
- 150
- Forks
- 41
- Avg merge
- 1d 9h
- Merged PRs (30d)
- 28
Description
We should add support to reset_aggregated_jumps! such that it can take the indices of updated parameters and/or unknowns, and call into an aggregator via a dispatch to make more minimal updates for what has changed (instead of completely reinitializing). This would likely be much more performant for methods like RSSACR that have big data structures they rely on.
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 locating reset_aggregated_jumps! and the existing aggregator implementations. Trace how parameter and unknown updates currently cause reinitialization, then determine the dispatch boundary for incremental updates. Done means updated indices can be passed through and aggregators perform minimal updates without complete reinitialization, with appropriate tests or benchmarks.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- julia
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100