[Bridges] maintenance of zero_one.jl #1574
Conversation
| value, | ||
| ) where {T} | ||
| MOI.set(model, attr, bridge.integer_index, value) | ||
| MOI.set(model, attr, bridge.interval_index, value) |
There was a problem hiding this comment.
@blegat does ConstraintPrimalStart make sense for a ZeroOne constraint?
There was a problem hiding this comment.
Yes, a ConstraintPrimalStart is the starting value of the function. It's well-defined for all constraints
There was a problem hiding this comment.
Sure. But does any solver actually implement it...
There was a problem hiding this comment.
Since most solvers only support VariableIndex-in-Integer, and setting the starting value of this is a bit redundant, I don't think so. However, if a solver want to implemented ScalarAffineFunction in Integer, they will need this.
There was a problem hiding this comment.
To rephrase: in what situation would a solver benefit from being able to set ConstraintPrimalStart of a ZeroOne constraint.
There's a lot of stuff in MOI that is there "just because" without a good reason. Not that we shouldn't add some of the stuff. But if no one is ever going to call it, we shouldn't rush to add code. It's an overhead for everyone.
|
Merged for now. We can always revisit in the future. For now, |
2 participants
What does it mean to
ConstraintPrimalStartaZeroOneconstraint? We should only be supporting it if it makes sense.