-
Notifications
You must be signed in to change notification settings - Fork 2.4k
Lazy constraints in CPLEX and Gurobi #1381
Copy link
Copy link
Closed
Labels
Feature RequestMissing Feature/WrapperMissing Feature/WrapperSolver: CPLEXCPLEX Solver related issueCPLEX Solver related issueSolver: GurobiGUROBI Solver related issueGUROBI Solver related issueSolver: Linear SolverRelated to all Linear Solver (GLOP, BOP, CBC etc...)Related to all Linear Solver (GLOP, BOP, CBC etc...)
Milestone
Metadata
Metadata
Assignees
Labels
Feature RequestMissing Feature/WrapperMissing Feature/WrapperSolver: CPLEXCPLEX Solver related issueCPLEX Solver related issueSolver: GurobiGUROBI Solver related issueGUROBI Solver related issueSolver: Linear SolverRelated to all Linear Solver (GLOP, BOP, CBC etc...)Related to all Linear Solver (GLOP, BOP, CBC etc...)
Type
Fields
Give feedbackNo fields configured for issues without a type.
According to the documentation the only MIP solver that implements lazy constraints is SCIP:
or-tools/ortools/linear_solver/linear_solver.h
Line 971 in f3fd201
But reading through the code of
linear_solver.ccit looks as if the condition is passed in theMakeRowConstraintfunction:or-tools/ortools/linear_solver/linear_solver.cc
Line 616 in f3fd201
Is there any reason for it not to work with the other solvers?
My application relies on Lazy constraints and not being able to use them with these solvers may lead me not to use the or-tools interface.