AMReX-Astro / AMReX-Astro/Castro
make advection memory (largely) independent of number of species
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 340
- Forks
- 105
- Avg merge
- 3d 8h
- Merged PRs (30d)
- 8
Description
We should be able to reformulate the CTU method to do the species updates "on demand" by upwinding based on the contact speed (for non-HLL solvers), and therefore not need to store the fluxes of the species. We'll use this issue to explore this idea.
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
No file, test, or entry point is named. Start by locating the CTU advection implementation, species updates, and species-flux storage, then compare the non-HLL solver paths and contact-speed upwinding. Done should establish whether the reformulation avoids storing species fluxes while preserving the updates, with validation defined for the affected methods.
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
- 20/100