[Symphony-tickets] Re: [SYMPHONY] #67: stops prematurely on setting
upperbound using -u flag.
SYMPHONY
coin-trac at coin-or.org
Fri Apr 27 09:09:52 EDT 2007
#67: stops prematurely on setting upperbound using -u flag.
-----------------------+----------------------------------------------------
Reporter: asm4 | Owner: tkr
Type: defect | Status: closed
Priority: normal | Milestone: 5.2
Component: Not Sure | Version:
Resolution: invalid | Keywords:
-----------------------+----------------------------------------------------
Changes (by tkr):
* status: new => closed
* resolution: => invalid
Comment:
This is the correct behavior. Setting the upper bound flag means that a
solution with the given value has already been found. In this case,
SYMPHONY will only report solutions that are strictly better than the
existing one. If no such solution exists, it will report that the problem
is infeasible. In other words, it is like solving the original IP with the
additional constraint that the objective function value has to be strictly
below the one given.
--
Ticket URL: <https://projects.coin-or.org/SYMPHONY/ticket/67#comment:1>
SYMPHONY <http://projects.coin-or.org/SYMPHONY>
The SYMPHONY framework for parallel branch-and-cut algorithms.
More information about the Symphony-tickets
mailing list