Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update MOI Interface to use LinQuadOptInterface #110

Closed
ndinsmore opened this issue Feb 13, 2019 · 5 comments
Closed

Update MOI Interface to use LinQuadOptInterface #110

ndinsmore opened this issue Feb 13, 2019 · 5 comments

Comments

@ndinsmore
Copy link
Contributor

Sould Cbc be updated to use LinQuadOptInterface for it's MOI Interface? It looks like it could leverage alot of what Clp.jl has done and would make maintaining and upgrading both easier.

Has this already been discussed?

@mlubin
Copy link
Member

mlubin commented Feb 13, 2019

What are the current maintenance issues with the Cbc MOI wrapper and how would they be addressed by using LinQuadOptInterface? IMO using LinQuadOptInterface should not be the preferred choice for interfaces because it adds another layer between JuMP and the solver that's not as well documented as plain MOI.

@odow
Copy link
Member

odow commented Feb 13, 2019

LinQuadOptInterface assumes that variables and constraints can be added on-demand. The Cbc C interface (until recently) requires everything at once.

@ndinsmore
Copy link
Contributor Author

I wouldn't say that there are any maintenance issues per se. But in looking at capabilities CBC ~= GLPK, so while trying to figure out what it would take to add dual capability to Cbc, I was looking at GLPK and Clp both of which use LQOI. Cbc has actually modeled it's interface after CLP so I thought I would ask.

@mlubin
Copy link
Member

mlubin commented Feb 13, 2019

Supporting duals means implementing the ConstraintDual attribute. That's about it from the perspective of the MOI interface. The bigger issue is getting these values from Cbc.

@mlubin
Copy link
Member

mlubin commented Jun 28, 2019

We don't plan to rewrite the interface to LQOI. Both Gurobi and GLPK are moving away from LQOI.

@mlubin mlubin closed this as completed Jun 28, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Development

No branches or pull requests

3 participants