Split "minimize" and "maximize"
|Reported by:||hpwalton||Owned by:||hpwalton|
Description (last modified by hpwalton)
Motivation: It is difficult to do special things like SOS currently. SOS requires observation of data in the matrix before it can be set up properly. However, it must be done before the call to solve();
Another symptom of this is the "writeMPS" call in the midst of the code commented out.
The client of the model could call that on their own if they had a moment break in between the generation and the solving of the model
split "minimize"/"maximize"/... into a few bits:
If absolutely necessary, I can fabricate minimize() and maximize() to behave as they do today. This is a little tricky, but can be done.
This would also allow folks to simply generate an MPS/LP file while debugging the model readily. I find this to be extraordinarily helpful.
May also need "detach()" -- discussion point.