solver:objective_of_fixed_model_is_different_than_the_reported_mip_solution

This shows you the differences between two versions of the page.

Next revision | Previous revision | ||

solver:objective_of_fixed_model_is_different_than_the_reported_mip_solution [2011/05/31 22:35] support created |
— (current) | ||
---|---|---|---|

Line 1: | Line 1: | ||

- | ====== Objective of fixed model is different than the reported MIP solution ====== | ||

- | Running the model [[http://www.gams.com/modlib/libhtml/rotdk.htm|rotdk]] with GAMS/Cplex yields: | ||

- | <code> | ||

- | Solution satisfies tolerances. | ||

- | |||

- | MIP Solution: 2012.831285 (802 iterations, 0 nodes) | ||

- | Final Solve: 2008.641285 (0 iterations) | ||

- | |||

- | Best possible: 1921.405150 | ||

- | Absolute gap: 91.426136 | ||

- | Relative gap: 0.045422 | ||

- | </code> | ||

- | |||

- | If a MIP has continuous variables, the objective of the fixed model can differ from objective value reported when the incumbent solution was first found. This can happen because CPLEX has many different procedures to derive integer feasible solutions. Some of them provide an optimal basis to a node LP that will also be optimal for the fixed problem, but others do not. In the latter case, changes to the continuous variables in the fixed model may yield an improvement in the objective and this is what is happening with the model. ([[http://www-01.ibm.com/support/docview.wss?uid=swg21399941|reference]]). | ||

- | |||

- | This behavior will disappear, if you set optca/optcr to Zero. |

IMPRESSUM / LEGAL NOTICE
PRIVACY POLICY
solver/objective_of_fixed_model_is_different_than_the_reported_mip_solution.1306874131.txt.gz ยท Last modified: 2011/05/31 22:35 by support