Changes between Version 1 and Version 3 of Ticket #20462


Ignore:
Timestamp:
05/23/16 20:30:56 (3 years ago)
Author:
mkoeppe
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #20462

    • Property Cc jdemeyer added
    • Property Authors changed from to Matthias Koeppe
  • Ticket #20462 – Description

    v1 v3  
    1010The bug is in `MIPVariable.set_min`, `.set_max`, which calls back into the problem to change the bounds of *all* variables of the problem rather than just its components.
    1111
    12 Oh, and why does a `MIPVariable` only have `set_max`, but no `get_max`?
    13 And why all of that bizarre delegating to `MIPVariable` when other `MixedIntegerLinearProgram` methods such as `set_integer` etc. just do everything directly, and no corresponding `MIPVariable` methods exist?
    14 
    15 I guess this is also a great moment to mention that these things should properly be referred to as `lower_bound` and `upper_bound` rather than `min` and `max`. Some deprecation fun to be had.
    16 
    17 And why is there no way to query the values of the components of the `_default_mipvariable`?
    18