Cannot read file as JSON object
Nobody has claimed this yet.
- Dominant language
- Cuda
- Stars
- 692
- Forks
- 197
- PR merge metrics
- No merged PRs in 30d
Description
When I use amgx_capi to solve some sparse linear system, it comes out that most of the default configs cannot be loaded into the API. Some default config will be used and the number of AMG levels is set to be 1.
Cannot read file as JSON object, trying as AMGX config
Converting config string to current config version
For some large enough sparse systems, these default settings won't converge.
For instance, ../core/configs/FGMRES_AGGREGATION_JACOBI.json will be loaded, however, ../core/configs/FGMRES_CLASSICAL_AGGRESSIVE_HMIS.json and ../core/configs/AMG_CLASSICAL_L1_AGGRESSIVE_HMIS.json will not.
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
Reproduce the configuration loading through amgx_capi using the named files ../core/configs/FGMRES_AGGREGATION_JACOBI.json, FGMRES_CLASSICAL_AGGRESSIVE_HMIS.json, and AMG_CLASSICAL_L1_AGGRESSIVE_HMIS.json. Compare the loading path and reported AMG levels for the working and failing configurations; done means the failing defaults load as JSON objects without falling back to one AMG level.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- json
- Domain
- backend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100