Experiment with maximum order in VODE
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 25/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- cpp
- Domain
- hpc, performance
Research direction
Start in integration/VODE/vode_type.H at the hardcoded maximum order of 5. Experiment with a lower maximum-order limit and compare the tradeoff between per-step accuracy, per-step performance, GPU thread-local memory use, and overall burn time; done means the results support or reject lowering the limit.
Written by the indexing model from the issue text.
Description
The maximum order in VODE is hardcoded to 5. We should experiment to see what happens if we use a lower limit on maximum order. On GPUs thread-local memory is limited so it is possible that the tradeoff between per-step accuracy and per-step performance is worth it when considering the overall time of the burn.
- Dominant language
- C++
- Stars
- 44
- Forks
- 46
- Avg merge
- 3d 15h
- Merged PRs (30d)
- 9
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
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.
More from AMReX-Astro/Microphysics
-
bug GPU
Difficulty 2/5 1-3 hours Newbie friendliness 69/100
AMReX-Astro/Microphysics#2115 ·
Maintainers usually reply within 1 day
-
Difficulty 5/5 Over a week Newbie friendliness 25/100
AMReX-Astro/Microphysics#2104 · 3 comments ·
Maintainers usually reply within 1 day
-
ai-code-audit screening
Difficulty 4/5 3-5 days Newbie friendliness 55/100
AMReX-Astro/Microphysics#2097 · 1 comment ·
Maintainers usually reply within 1 day
-
ai-code-audit screening
Difficulty 4/5 3-5 days Newbie friendliness 72/100
AMReX-Astro/Microphysics#2096 ·
Maintainers usually reply within 1 day
-
ai-code-audit screening
Difficulty 4/5 3-5 days Newbie friendliness 66/100
AMReX-Astro/Microphysics#2095 · 1 comment ·
Maintainers usually reply within 1 day
All issues in AMReX-Astro/Microphysics
Similar issues
-
(S1 - Need confirmation)
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
CleverRaven/Cataclysm-DDA#89194 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
moonshine-ai/moonshine#231 ·
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
Maintainers usually reply within 1 day
-
documentation good first issue M7: multi-node no hardware needed
Difficulty 1/5 Under an hour Newbie friendliness 95/100
GageLawton/noise-cancellation#299 ·
Maintainers usually reply within 1 day