Testing Amgx binary
Nobody has claimed this yet.
- Dominant language
- Cuda
- Stars
- 692
- Forks
- 197
- PR merge metrics
- No merged PRs in 30d
Description
Hi,
We are new to this Amgx application. We came across Readme file in Amgx github, where under "running example" session. they have mentioned below example:
examples/amgx_capi -m ../examples/matrix.mtx -c ../src/configs/FGMRES_AGGREGATION.json
mpirun -n 2 examples/amgx_mpi_capi.exe -m ../examples/matrix.mtx -c ../src/configs/FGMRES_AGGREGATION.json
Seems like for amgx_capi, the second argument is matrix and it is being used together with the FGMRES_AGGREGATION.json file. For other targets(eg: Eigen_solver, amgx_mpi_capi, amgx_mpi_poisson7 etc) which json(GMRES_AGGREGATION.json , V-cheby-smoother.json, FGMRES_AGGREGATION_DILU.json etc ) is more suited as third argument? Is there is any mapping or documentation for all the test cases. kindly share.
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
Read the README's "Running Example" section and inspect the named targets: examples/amgx_capi, amgx_mpi_capi.exe, amgx_mpi_poisson7, and the configs under src/configs. Document which configuration files apply to the example targets and how the matrix and configuration arguments relate. Done means the README or a linked reference covers the requested test-case mapping.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100