<html><body>
<DIV>I've been trying to carefully control output by introducing my own message handler. It's been a bit tricky with CBC, but for the most part I could work around it.</DIV>
<DIV> </DIV>
<DIV>I'm using Cbc and Clp together. In order to capture the Clp output, I have to do something like this:</DIV>
<DIV><FONT size=2>
<P>OsiClpSolverInterface *lpSolver = </FONT><FONT color=#0000ff size=2>new</FONT><FONT size=2> OsiClpSolverInterface();<BR></FONT><FONT size=2>lpSolver->passInMessageHandler(logger); </FONT><FONT color=#008000 size=2><BR></FONT><FONT size=2>OsiCbcSolverInterface *ipSolver = </FONT><FONT color=#0000ff size=2>new</FONT><FONT size=2> OsiCbcSolverInterface(lpSolver);<BR>ipSolver->getModelPtr()->passInMessageHandler(logger); <BR></FONT><FONT size=2>ipSolver->passInMessageHandler(logger); </FONT></P>
<P><FONT size=2>This by itself is a bummer because I suspect that in other OsiSolverInterace conditions I can just hook up to the ipSolver....</FONT></P>
<P>Now, I've added some additional processing for "prefer round up". In the sample code there is a call to initialSolve() amongst other things.</P>
<P>The trouble I'm having is that once I call CbcModel::initialSolve(), all messages disappear. It appears to me as if something internal gets replaced or reset along the way and suddenly all output stops.</P>
<P>Any suggestions?</P>
<P>Philip</P>
<P><FONT size=2></FONT><FONT color=#008000 size=2> </P></FONT></DIV></body></html>