Investigate alternative ODE solver strategies
Open
Nobody has claimed this yet.
discretization
enhancement
- Dominant language
- C++
- Stars
- 245
- Forks
- 36
- Avg merge
- 8d 23h
- Merged PRs (30d)
- 4
Description
We should re-evaluate this interface strategy for ODE solvers. Tracking down the references and ownership of data can get confusing.
_Originally posted by @jamiebramwell in https://github.com/LLNL/serac/pull/827#discussion_r1000022713_
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 ODE solver interface strategy and the reference and ownership concerns described in the issue, then review the originating discussion in PR #827. Before implementation, define the alternative strategy and its ownership boundaries; the issue does not specify files, tests, or acceptance criteria.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- hpc
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100