You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
How should JuMP interface with the solver ? I see in the tests that the solver can receive the problem via an MPS file. Is there a way to specify it directly with a sparse matrix format ? Or do you think we should just communicate with an MPS file ?
No need for a high-level API for the purpose of having a JuMP interface. We have solve solver wrappers with high-level APIs but that's for legacy reason. For the new wrappers to C solvers, we prefer just having the MOI wrapper and the bindings generated by Clang. We do this to ease maintenance. Now, if you want the users to also be able to use cuPDLPx in Julia directly from a big sparse A matrix without JuMP, feel free to also add a high-level wrapper as well. Or just wait for a user having a concrete use case for it first :)
Thanks for the clarification. I also prefer to stick with just the MOI wrapper for easier maintenance, so I’ll leave a separate high-level wrapper out for now.
Activity
ZedongPeng commentedon Nov 28, 2025
In addition to MPS file support, we now have
create_lp_problemandsolve_lp_problemavailable for creating and solving LPs directly. I can add an example of this workflow to the tests.Btw, I haven't defined anything in
src/cuPDLPx.jl. Do I need to add a high-level wrapper there?https://github.com/MIT-Lu-Lab/cuPDLPx.jl/blob/a3e26bd11674a483f7caed4f878b6349e51e2f89/src/LibcuPDLPx.jl#L160-L174
blegat commentedon Nov 29, 2025
No need for a high-level API for the purpose of having a JuMP interface. We have solve solver wrappers with high-level APIs but that's for legacy reason. For the new wrappers to C solvers, we prefer just having the MOI wrapper and the bindings generated by Clang. We do this to ease maintenance. Now, if you want the users to also be able to use cuPDLPx in Julia directly from a big sparse
Amatrix without JuMP, feel free to also add a high-level wrapper as well. Or just wait for a user having a concrete use case for it first :)ZedongPeng commentedon Nov 29, 2025
Thanks for the clarification. I also prefer to stick with just the MOI wrapper for easier maintenance, so I’ll leave a separate high-level wrapper out for now.
blegat commentedon Jan 30, 2026
Closing as this is done now :)