<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<font size="-1">Hi andrew,<br>
<br>
<font size="-1"><font size="-1">Thanks for your message,<br>
<br>
With diving options, <font size="-1">the problem is solved in 7 minutes (454 sec).
<font size="-1">These options seems to be very efficient!<br>
<font size="-1">I just don't know if i can u<font size="-1">se them for <font size="-1">
a</font>ny kin<font size="-1">d of </font>problem and if not, how to decide to use them or not.<br>
<br>
<font size="-1">For warm start<font size="-1">s, i <font size="-1">have actually no idea how i can constrain
<font size="-1">our <font size="-1">problems. I will think about it.<br>
<br>
<font size="-1">Thank again for your help.<br>
<br>
<font size="-1">Yves</font><br>
</font></font></font></font></font></font></font></font></font></font><br>
</font></font></font>
<div class="moz-cite-prefix">On 11/04/2014 03:41 AM, Andrew Wald wrote:<br>
</div>
<blockquote cite="mid:CADbqYTKr-6+B9wfLuCUOzg2-8H_nqmixE0nTTiP429DZwiiBtA@mail.gmail.com" type="cite">
<div dir="ltr">Hi Yves,
<div><br>
</div>
<div>I don't claim to be an expert with Cbc, but I used a couple techniques that were successful in my last project.<br>
</div>
<div><br>
</div>
<div>I had a pretty large workforce optimization problem that was wholly intractable with Cbc; it took forever to reach even a 5% optimality gap with CPLEX. Apart from throwing more computer at the problem, I found the following to be helpful:</div>
<div><br>
</div>
<div>1) Try experimenting with different combinations of diving options. I ran a bunch of tests and found that DivingVectorlength, by itself, was the most effective for my formulation. </div>
<div>2) Try warm starts. I overly constrained my problem to something Cbc could solve relatively quickly, which I then plugged back in as a feasible integer starting point for the next run (where those constraints were relaxed). This is what took me from intractability
to something that Cbc could churn through.</div>
<div><br>
</div>
<div>I hope this helps with your particular problem,</div>
<div>Andrew Wald</div>
<div><br>
</div>
<div><br>
</div>
</div>
<div class="gmail_extra"><br>
<div class="gmail_quote">On Mon, Nov 3, 2014 at 5:02 AM, Yves Touchard <span dir="ltr">
<<a moz-do-not-send="true" href="mailto:ytouch@dxo.com" target="_blank">ytouch@dxo.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">
<div bgcolor="#FFFFFF" text="#000000"><font size="-1">Hello,<br>
<br>
<font size="-1">I have a (huge, </font></font><font size="-1"><font size="-1"><font size="-1"><font size="-1">more than one million of lines...</font></font>) constraint file (</font></font><small><a moz-do-not-send="true" href="https://www.dropbox.com/s/6y7oid24ecv8oh7/huge.lp?dl=0" target="_blank">https://www.dropbox.com/s/6y7oid24ecv8oh7/huge.lp?dl=0</a></small><font size="-1"><font size="-1">)
<font size="-1">taking a lo<font size="-1">n<font size="-1">g time (aroun<font size="-1">d 4 hours) to be solved<font size="-1"> (</font>Log file</font></font></font></font></font>:<font size="-1">
</font></font><small><a moz-do-not-send="true" href="https://www.dropbox.com/s/rx7m8xtzbe9wsd8/huge.log.txt?dl=0" target="_blank">https://www.dropbox.com/s/rx7m8xtzbe9wsd8/huge.log.txt?dl=0</a>)<br>
I understand that such a huge file could be tricky for the solver. So, what is the best solution:<br>
</small>
<ul>
<li><small>Doing a pre-analysis to split the problem in two or more sub-problems.</small>
</li><li><small>Use specific options to reduce elapsed time (in a deterministic way - such as gap). I tried with diving options but there was a memory allocation error (<a moz-do-not-send="true" href="https://www.dropbox.com/s/rd00y6mfapedq17/hugeErr.log.txt?dl=0" target="_blank">https://www.dropbox.com/s/rd00y6mfapedq17/hugeErr.log.txt?dl=0</a>)</small>
</li><li><small>Let you search and find if there is a way to speed up the coin process.</small>
</li></ul>
<p><small>Thanks and regards,<br>
</small></p>
<p><small>Yves Touchard</small><br>
</p>
<br>
<font color="Black" face="Arial">------------------------------------------------------------------------------<br>
This message and any attachments (the "message") are confidential and intended solely for the addressee(s). Any unauthorized use or dissemination is prohibited. E-mails are susceptible to alteration. Neither DxO Labs nor any of its subsidiaries or affiliates
shall be liable for the message if altered, changed or falsified.<br>
Ce message et toutes les pièces jointes (ci-après le "message") sont confidentiels et établis à l'intention exclusive de ses destinataires. Toute utilisation ou diffusion non autorisé est interdite. Tout message électronique est susceptible d'altération. DxO
Labs et ses filiales déclinent toute responsabilité au titre de ce message s'il a été altéré, modifié ou falsifié.<br>
</font></div>
<br>
_______________________________________________<br>
Cbc mailing list<br>
<a moz-do-not-send="true" href="mailto:Cbc@list.coin-or.org">Cbc@list.coin-or.org</a><br>
<a moz-do-not-send="true" href="http://list.coin-or.org/mailman/listinfo/cbc" target="_blank">http://list.coin-or.org/mailman/listinfo/cbc</a><br>
<br>
</blockquote>
</div>
<br>
</div>
</blockquote>
<br>
<br>
<font face="Arial" color="Black" size="2">------------------------------------------------------------------------------<br>
This message and any attachments (the "message") are confidential and intended solely for the addressee(s). Any unauthorized use or dissemination is prohibited. E-mails are susceptible to alteration. Neither DxO Labs nor any of its subsidiaries or affiliates
shall be liable for the message if altered, changed or falsified.<br>
Ce message et toutes les pièces jointes (ci-après le "message") sont confidentiels et établis à l'intention exclusive de ses destinataires. Toute utilisation ou diffusion non autorisé est interdite. Tout message électronique est susceptible d'altération. DxO
Labs et ses filiales déclinent toute responsabilité au titre de ce message s'il a été altéré, modifié ou falsifié.<br>
</font>
</body>
</html>