Closed dslove closed 9 months ago
I solved this recently by just setting ortools to version < 9.5.0 manually
I solved this recently by just setting ortools to version < 9.5.0 manually
Thanks. Yes I know it can be fixed this way. This ticket is just to maybe find out the root cause.
I think CVXPY does not support the latest versions of ortools yet. However, CVXPY is only used for piecewise continuous binning, and the solver used is not ortools CP (only ECOS, HIGHS and OSQP). The cornerstone of optbinning is the ortools CP, so it will always require the latest version of ortools to use the most performant solver.
See also this PR at cvxpy to fix the issue. I think it's not included in a release yet, but should fix things when it is. (I suppose it'd be worth checking by installing their main branch and rerunning a test script here?)
Seems cvxpy had a release 1.4.1 on last Thursday (10/12) which can be picked up now.
Thanks @dslove!
When running my program using
optbinning
I got a warning after upgrading from0.15.0
to0.18.0
:I didn't open this issue to
cvxpy
in the first place because this happened after I upgradedoptbinning
and what confuses me is thatcvxpy
doesn't sound usingortools
according to the dependency tree. I wonder if the problem might be in optbinning.