<br><font size=2 face="sans-serif">The reason I dislike OsiCbc is that
it uses other OsiXxx solvers so there is no clean structure. If you
do OsiCbcSolverInterface::branchAndBound it calls Cbc's branch and bound
which uses a OsiXxxSolverInterface solver. To make things even worse
this underlying solver could be OsiCbcSolverInterface!! (eventually a real
solver would be called).</font>
<br>
<br><font size=2 face="sans-serif">Also it is difficult to tune as apart
from CbcStrategy it only has OsiXxxSolverInterface methods.</font>
<br>
<br><font size=2 face="sans-serif">The status of OsiCbc will always be
- it will work - but it will not easily take advantage of new ideas in
Cbc or tuning parameters.</font>
<br>
<br><font size=2 face="sans-serif">John Forrest</font>
<br>
<br>
<br>
<table width=100%>
<tr valign=top>
<td width=40%><font size=1 face="sans-serif"><b>Matthew Saltzman <mjs@clemson.edu></b>
</font>
<br><font size=1 face="sans-serif">Sent by: coin-discuss-bounces@list.coin-or.org</font>
<p><font size=1 face="sans-serif">03/09/2007 11:15 AM</font>
<table border>
<tr valign=top>
<td bgcolor=white>
<div align=center><font size=1 face="sans-serif">Please respond to<br>
Discussions about open source software for Operations Research
<coin-discuss@list.coin-or.org></font></div></table>
<br>
<td width=59%>
<table width=100%>
<tr valign=top>
<td>
<div align=right><font size=1 face="sans-serif">To</font></div>
<td><font size=1 face="sans-serif">Discussions about open source software
for Operations Research <coin-discuss@list.coin-or.org></font>
<tr valign=top>
<td>
<div align=right><font size=1 face="sans-serif">cc</font></div>
<td>
<tr valign=top>
<td>
<div align=right><font size=1 face="sans-serif">Subject</font></div>
<td><font size=1 face="sans-serif">Re: [Coin-discuss] OsiCbcSolverInterface
turn off log messages</font></table>
<br>
<table>
<tr valign=top>
<td>
<td></table>
<br></table>
<br>
<br>
<br><tt><font size=2>On Fri, 9 Mar 2007, Tim Hultberg wrote:<br>
<br>
> What?!<br>
><br>
> I am very sorry to hear this. When I first wrote flopc++, I interfaced<br>
> directly with Cplex. Then I discovered Coin-OSI, and was able to change<br>
> solver easily without writing new interfaces each time. Now I use
OsiCbc<br>
> as solver in the flopc++ example MIP models (or OsiClp, if its an
LP),<br>
> such that they can be compiled and executed without using anything<br>
> external to Coin.<br>
><br>
> I think it makes sense to keep a strong and up to date OsiCbc in Coin,<br>
> so maybee this is a good candidate for the help wanted list. (Or should<br>
> I use OsiSym instead?)<br>
<br>
I agree that this should be a priority (for exactly this reason), and it
<br>
would be great to have a brave volunteer to take it on.<br>
<br>
><br>
> Tim Hultberg<br>
><br>
><br>
>>>> John J Forrest <jjforre@us.ibm.com> 09/03/2007 16:14
>>><br>
> By the way - the use of OsiCbc is deprecated - there is much more<br>
> functionality and performance using Cbc and OsiClp.<br>
><br>
> John Forrest<br>
><br>
><br>
><br>
><br>
> _______________________________________________<br>
> Coin-discuss mailing list<br>
> Coin-discuss@list.coin-or.org<br>
> http://list.coin-or.org/mailman/listinfo/coin-discuss<br>
><br>
<br>
-- <br>
Matthew Saltzman<br>
<br>
Clemson University Math Sciences<br>
mjs AT clemson DOT edu<br>
http://www.math.clemson.edu/~mjs<br>
_______________________________________________<br>
Coin-discuss mailing list<br>
Coin-discuss@list.coin-or.org<br>
http://list.coin-or.org/mailman/listinfo/coin-discuss<br>
</font></tt>
<br>