<br><font size=2 face="sans-serif">Tim,</font>
<br>
<br><font size=2 face="sans-serif">It is a "feature" - there
may be a bug but not where you think.</font>
<br>
<br><font size=2 face="sans-serif">When Osl finds a solution it sets a
"bound" of solution - epsilon (default 1.0e-5). OsiOsl
picks up this and stores it so in this case it is as if </font>
<br>
<br><font size=2 face="sans-serif">Solver->setDblParam(OsiDualObjectiveLimit,-1.0e-5);</font>
<br>
<br><font size=2 face="sans-serif">After second branch and bound the test
for provenOptimal etc tests objective value of 0.0 against -1.0e-5 and
says not optimal which is correct.</font>
<br>
<br><font size=2 face="sans-serif">To get the behavior you want add this
before second solve.</font>
<br>
<br><font size=2 face="sans-serif">Solver->setDblParam(OsiDualObjectiveLimit,1.0e50);</font>
<br>
<br><font size=2 face="sans-serif">The bug? Osl seems to say that
it found an optimal solution when it should not have. I will look
into it to see if OsiDualObjectiveLimit is not being passed in to Osl correctly.</font>
<br>
<br><font size=2 face="sans-serif">John Forrest</font>
<br>