<div dir="ltr"><div>This does sound like a bug in the pre-processor. The pre-processor is a relatively new addition to SYMPHONY. Can you share an instance file that demonstrates this off-line?<br><br></div>Cheers,<br><br>Ted<br>
</div><div class="gmail_extra"><br><br><div class="gmail_quote">On Tue, May 20, 2014 at 9:19 AM, Mikko Alinikula - SUBNIC OY <span dir="ltr"><<a href="mailto:subnic@kolumbus.fi" target="_blank">subnic@kolumbus.fi</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hello Ted,<br>
<br>
I calculate the my truss-problem in 2 phases. First a fixed-geometry-solution is optimized with SYMPHONY and it takes around 100 ms to get a solution. In phase 2 I input that solution as a initial solution using sym_set_col_solution-function to calculate the real problem.<br>
<br>
I got this working with small models but larger models with 1000 variables or so crashed when I called sym_solve. Sometimes a memory error was issued but more often the system just crashed.<br>
<br>
But there seems to be a workaround to this .. if I set sym_set_int_param(env, "prep_level", 0) I got the system working with models having more than 3000 variables and 10000 restricting equations.<br>
<br>
Maybe there is a bug in the preprosessor in the Win32-environment?<br>
<br>
BR<br>
<br>
Mikko<br>
<br>
______________________________<u></u>_________________<br>
Symphony mailing list<br>
<a href="mailto:Symphony@list.coin-or.org" target="_blank">Symphony@list.coin-or.org</a><br>
<a href="http://list.coin-or.org/mailman/listinfo/symphony" target="_blank">http://list.coin-or.org/<u></u>mailman/listinfo/symphony</a><br>
</blockquote></div><br><br clear="all"><br>-- <br>Dr. Ted Ralphs<br>Associate Professor, Lehigh University<br>(610) 628-1280<br>ted 'at' lehigh 'dot' edu<br><a href="http://coral.ie.lehigh.edu/~ted" target="_blank">coral.ie.lehigh.edu/~ted</a><br>
</div>