-
-
Notifications
You must be signed in to change notification settings - Fork 705
Description
Follow-up on #20462:
-
MIPVariable: Better names for backend variables #31791
MIPVariable: Better names for backend variables -
MIPVariable: Change to a subclass of FiniteFamily #31750
MIPVariable: Change to a subclass ofFiniteFamily -
MixedIntegerLinearProgram: New generator method 'variables' #31749
MixedIntegerLinearProgram: New generator methodvariables -
A MIPVariable's repr should include some useful information #20331 A
MIPVariable's repr should include some useful information -
MixedIntegerLinearProgram: Remove _variables dictionary #20656
MixedIntegerLinearProgram: Remove_variablesdictionary -
MixedIntegerLinearProgram should provide a way to get the variables in the order they are provided to the polyhedron method #26302
MixedIntegerLinearProgramshould provide a way to get the variables in the order they are provided to thepolyhedronmethod -
Setting a default max/min bound when calling MixedIntegerLinearProgram.new_variable #7790 Setting a default max/min bound when calling
MixedIntegerLinearProgram.new_variable -
More fixes for copying a MIP and the MIPVariables created by new_variable #20657: More fixes for copying a
MIPand theMIPVariablescreated bynew_variable -
Why does a
MIPVariableonly haveset_max, but noget_max? -
Why does
MixedIntegerLinearProgram.set_maxdelegate to aMIPVariablemethod of the same name, when otherMixedIntegerLinearProgrammethods such asset_integeretc. just do everything directly, and no correspondingMIPVariablemethods exist? -
Actually these things should properly be referred to as
lower_boundandupper_boundrather thanminandmax. Some deprecation fun to be had. -
Why is there no way to query the values of the components of the
_default_mipvariable?
Depends on #20462
CC: @dimpase @videlec @jdemeyer @yuan-zhou
Component: numerical
Issue created by migration from https://trac.sagemath.org/ticket/20664