External — MadNLPGPU integration (in the MadNLP repository)
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 35/100
Research direction
First confirm that #27 has merged, then read the External section of TASKS.md on main alongside the PLAN.md sections it names and the previous tasks' Report blocks. In the MadNLPGPU repository, inspect CUDSSSolver and the specified task details; done means a pglib case matches cuDSS within ±2 iterations and reaches the same final objective within 1e-6.
Written by the indexing model from the issue text.
Description
Task External of TASKS.md — milestone M4 — Symmetric indefinite LDLᵀ/LDLᴴ (MadNLP-ready).
Depends on: #27 (T27) must be merged first; tasks are strictly sequential.
Summary (from TASKS.md): Add a SparseDirectSolver-backed AbstractLinearSolver next to CUDSSSolver (after T15; batch support after T17); test: a pglib case solves with the same iteration count ±2 as with cuDSS and the same final objective to 1e-6.
Scope and deliverables: the section External of TASKS.md on main is the single source of truth; it is not copied here so it cannot drift. Read it together with the PLAN.md sections it names and the Report blocks of the previous tasks.
This task lives in the MadNLP repository (MadNLPGPU). It is tracked here for the milestone only and is not chained by the Claude pipeline.
Generated by Claude Code
- Dominant language
- Julia
- Stars
- 3
- Forks
- 0
- Avg merge
- 3h 2m
- Merged PRs (30d)
- 65
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- No contributing guide
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 exanauts/SparseDirectSolver.jl
-
task
Difficulty 5/5 Over a week Newbie friendliness 12/100
exanauts/SparseDirectSolver.jl#118 ·
Maintainers usually reply within 1 day
-
task
Difficulty 4/5 3-5 days Newbie friendliness 20/100
exanauts/SparseDirectSolver.jl#117 ·
Maintainers usually reply within 1 day
-
task
Difficulty 5/5 Over a week Newbie friendliness 8/100
exanauts/SparseDirectSolver.jl#116 ·
Maintainers usually reply within 1 day
-
task
Difficulty 5/5 Over a week Newbie friendliness 8/100
exanauts/SparseDirectSolver.jl#115 ·
Maintainers usually reply within 1 day
-
found-by-agent triaged
Difficulty 5/5 Over a week Newbie friendliness 12/100
exanauts/SparseDirectSolver.jl#112 · 1 comment ·
Maintainers usually reply within 1 day
All issues in exanauts/SparseDirectSolver.jl
Similar issues
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
Maintainers usually reply within 2 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
JuliaPy/CondaPkg.jl#232 ·
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
SciML/PETScDiffEq.jl#196 ·
Maintainers usually reply within 1 day
-
Two jump tests solve a different problem than the one they buildPossibly taken A pull request linked to this issue is open or already merged. Open
Difficulty 1/5 1-3 hours Newbie friendliness 84/100
SciML/Catalyst.jl#1571 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 1 day