Skip to content

JuMP interface #3

Closed
Closed

Description

@blegat

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 ?

Activity

  1. ZedongPeng commented on Nov 28, 2025

    @ZedongPeng
    Collaborator

    In addition to MPS file support, we now have create_lp_problem and solve_lp_problem available 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

  2. blegat commented on Nov 29, 2025

    @blegat
    CollaboratorAuthor

    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 :)

  3. ZedongPeng commented on Nov 29, 2025

    @ZedongPeng
    Collaborator

    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.

  4. blegat commented on Jan 30, 2026

    @blegat
    CollaboratorAuthor

    Closing as this is done now :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions