solver:terminating_the_optimization_after_the_first_feasible_solution
Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision | |||
|
solver:terminating_the_optimization_after_the_first_feasible_solution [2020/10/29 15:43] Atharv Bhosekar removed |
— (current) | ||
|---|---|---|---|
| Line 1: | Line 1: | ||
| - | ====== MIP: Terminating the optimization after the first feasible solution ====== | ||
| - | Q: // Which GAMS or Cplex option can I use to make the solver stop quickly once a feasible solution has been found?// | ||
| - | |||
| - | |||
| - | On the GAMS level you can set ''optcr'' and ''optca'' to large numbers. If the bound and the value are on opposite sides of zero, this might result in larger values than one for ''optcr''. For setting ''optca'' large enough you need some idea about the range of objective values. In GAMS/CPLEX there is also an option called ''intsollim''. Setting ''intsollim'' to 1 will terminate the optimization after the first feasible integer solution. | ||
IMPRESSUM / LEGAL NOTICE
PRIVACY POLICY
solver/terminating_the_optimization_after_the_first_feasible_solution.1603982632.txt.gz ยท Last modified: 2020/10/29 15:43 by Atharv Bhosekar
Page Tools
Except where otherwise noted, content on this wiki is licensed under the following license: CC Attribution-Noncommercial-Share Alike 4.0 International
