<br><br><div class="gmail_quote">On Wed, Jan 6, 2010 at 7:58 AM, Ashutosh Mahajan <span dir="ltr"><<a href="mailto:asm4@lehigh.edu">asm4@lehigh.edu</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div class="im">On Mon, 04 Jan 2010, <a href="mailto:sj10@cs.brown.edu">sj10@cs.brown.edu</a> wrote:<br>
<br>
> Hey,<br>
><br>
> I'm trying to extract Gomory cuts out of Cgl using the following code -<br>
><br>
> OsiCuts cutlist;<br>
> CglGomory * gomory = new CglGomory();<br>
> //gomory->setLimit(100);<br>
> gomory->generateCuts(*sym, cutlist) ;<br>
><br>
> where sym is the OsiSymSolverInterface.<br>
><br>
> Unfortunately the generateCuts method is segfaulting. The same thing is<br>
> happening for the CglProbing cuts.<br>
<br>
</div>you need to use OsiClpSolverInterface instead of OsiSymSolverInterface. Gomory<br>
cuts are generated from the simplex tableau obtained by an LP solver like Clp.<br>
Symphony is an MILP solver. Similarly, CglProbing work with an LP solver only.<br>
<br>
cheers.<br>
<font color="#888888">ashutosh<br>
<br></font></blockquote><div><br>Thanks for the reply. Unfortunately now the loadProblem method of OsiClpSolverInterface is segfaulting. According to the Doxygen docs, the signature for the loadProblem method in OsiSymSolverInterface and OsiClpSolverInterface is the same and they both accept column major representation of the matrix.<br>
<br> Do you know why this might be happening? <br></div></div><br>Thanks<br>Sid<br>