AMG2023 status
Open
@rfhaque is already working on this.
Since Sep 4, 2025.
experiment
- Dominant language
- Python
- Stars
- 78
- Forks
- 52
- Avg merge
- 4d 19m
- Merged PRs (30d)
- 10
Description
Components
- Source code, Build system: CMake, Hypre uses Autotools. Debugging Problem 2 issue - Arjun and Rui Peng to debug mid-June.
- Source code released
- Spack package.py
- Ramble application.py
- Benchpark experiment.py
- +cuda experiment.py: Link errors for cublas #1067
- +rocm experiment.py: Tuolumne build error #1068 -- seems to be resolved?
- Dependencies: Hypre, Umpire. Umpire currently not on #1069 https://github.com/LLNL/AMG2023/pull/14 #1075. OOM error https://github.com/LLNL/AMG2023/issues/15 https://github.com/hypre-space/hypre/pull/1421. Allocation outside of the memory pool in Setup https://github.com/LLNL/AMG2023/issues/16. @rfhaque to follow up with Rui Peng. https://github.com/hypre-space/hypre/pull/1421. https://github.com/llnl/AMG2023/pull/17
- small test size problem for CI
- Scaling (Weak, Strong, or both)
- Large scale problem size defined. @rfhaque to follow up with Arjun.
- CI running on CPUs/CDash
- CI running on NVIDIA GPUs/CDash
- CI running on AMD GPUs/CDash
- +single_memory experiment.py: will not pursue
- +caliper experiment.py
- CPU-only performance analysis: Dane FOM low for Problem 1 #1070
- CUDA performance analysis
- ROCm performance analysis
- Documentation (build, run instructions, performance demo): https://lanl.github.io/benchmarks/02_amg/amg.html
- https://github.com/llnl/benchpark/issues/875
- Integer overflow #1252
- MPI bug in Problem 2 https://github.com/llnl/AMG2023/pull/18, also hangs - use STAT to diagnose where.
- Need to test AMG2023 as part of Hypre testing so it is not out of date
- Core dump on 64 nodes, 256 ranks, 360^3 elements. Different problem sizes fails at different node count. Need to give Arjun the logs
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.
Assessment
This issue has not been assessed yet.