AMReX-Astro / AMReX-Astro/Castro
implement use_retry for true-SDC
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 340
- Forks
- 105
- Avg merge
- 3d 8h
- Merged PRs (30d)
- 8
Description
Using this issue to keep track of what's necessary. My initial thought is that we don't really need to backup any part of the advance. If we run into an issue we just restart from the beginning with the new timestep, and reinitialize all of the stage data.
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
The payload names no files or tests; first locate the true-SDC implementation and its current use_retry handling. Read the surrounding timestep and stage-data lifecycle, then validate that a retry restarts from the beginning with the new timestep and reinitializes all stage data, as described.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- hpc
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100