<html><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class="">Hi all,<div class=""><br class=""></div><div class="">I’m encountering this issue again. It appears that the function SCIPlpShrinkRows is removing my rows and they are not added back. Hence I’m generating identical cuts in different nodes. I have set removable to false but my cuts are still removed. Is there a way to stop my rows being removed or somehow force them back in after jumping nodes?</div><div class=""><br class=""></div><div class="">I have another issue. In the context of column generation, I think there is a bug in separating constraints instead of separating cuts. After adding a constraint, SCIP solves the LP relaxation which could be infeasible. If infeasible, SCIP immediately exits and doesn’t proceed to another round of pricing. If I remember correctly, it sets the lower bound to infinity and it exits by bound. I didn’t write down exactly which part of the code this happens. I’ve been separating cuts instead, which runs correctly.</div><div class=""><br class=""></div><div class="">Cheers</div><div class=""><div class="">
Eddie
</div>
<div><br class=""><blockquote type="cite" class=""><div class="">On 8 May 2019, at 3:36 pm, Gregor Hendel <<a href="mailto:hendel@zib.de" class="">hendel@zib.de</a>> wrote:</div><br class="Apple-interchange-newline"><div class="">
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8" class="">
<div text="#000000" bgcolor="#FFFFFF" class="">
Hi list,<br class="">
<br class="">
Eddie and I discussed the subject in person some time ago, I just
repeat the conclusion.<br class="">
<br class="">
By separating a constraint such as setppc or knapsack instead of an
LP row, you have more control of the behavior of this constraint
through the use of its flags. After separating a constraint from
within a separator, this constraint will be immediately added as a
row to the LP relaxation, as well, as long as the "separate" flag is
set to TRUE for the new constraints. <br class="">
It is generally good if you can detect a constraint type that is
more special than just linear, and create the corresponding
constraint. A knapsack constraint, as an example, has much stronger
propagation algorithms than its linear equivalent. In the pricing
context, however, many possible deductions cannot be made on
constraints that are modifiable. <br class="">
<br class="">
Contrary to Eddie's assumption, there is no advantage in separating
constraints instead of rows w.r.t. the primal heuristic behavior.
Infact, the default primal heuristics of SCIP consider mostly the LP
relaxation for their decisions, but do not consider specific
constraint types at all. <br class="">
<br class="">
Best,<br class="">
Gregor<br class="">
<br class="">
<div class="moz-cite-prefix">Am 19.02.19 um 22:55 schrieb Edward
Lam:<br class="">
</div>
<blockquote type="cite" cite="mid:3BC1BF3A-4E61-4662-B9E4-0ADEAD01D08D@ed-lam.com" class="">
<meta http-equiv="content-type" content="text/html; charset=UTF-8" class="">
<div dir="ltr" class=""><font class=""><span style="caret-color:
rgb(0, 0, 0); background-color: rgba(255, 255, 255, 0);" class="">Hi
all,<br class="">
<br class="">
I have a constraint handler that is adding setppc
constraints (not rows/cuts) in the enfolp callback. I expect
the setppc constraint to then add a row into the LP. It
appears that sometimes this row is not in the LP (or
removed) so my separator is adding a duplicate setppc
constraint.</span></font></div>
<div dir="ltr" class=""><font class=""><span style="caret-color:
rgb(0, 0, 0); background-color: rgba(255, 255, 255, 0);" class=""><br class="">
</span></font></div>
<div dir="ltr" class=""><font class=""><span style="caret-color:
rgb(0, 0, 0); background-color: rgba(255, 255, 255, 0);" class="">This
also occurs when I tried separating rows directly. Sometimes
they are not in the LP, so I’m separating the same rows
again.<br class="">
<br class="">
Why does this occur? Is there a way to tell SCIP to simply
add the existing row back into the LP?</span></font></div>
<div dir="ltr" class=""><font class=""><span style="caret-color:
rgb(0, 0, 0); background-color: rgba(255, 255, 255, 0);" class=""><br class="">
</span></font></div>
<div dir="ltr" class=""><font class=""><span style="caret-color:
rgb(0, 0, 0); background-color: rgba(255, 255, 255, 0);" class="">Also,
is there any benefit to separating constraints vs. rows? I
assume constraints will improve primal heuristics and
propagation. Although I’m not sure what can be propagated in
column generation since setting a variable to 0 will
regenerate that column and setting it to 1 will prevent
future better columns from generating.<br class="">
<br class="">
Thanks in advance.<br class="">
<br class="">
Cheers<br class="">
Eddie</span></font></div>
<br class="">
<fieldset class="mimeAttachmentHeader"></fieldset>
<pre class="moz-quote-pre" wrap="">_______________________________________________
Scip mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Scip@zib.de">Scip@zib.de</a>
<a class="moz-txt-link-freetext" href="https://listserv.zib.de/mailman/listinfo/scip">https://listserv.zib.de/mailman/listinfo/scip</a>
</pre>
</blockquote>
<br class="">
</div>
_______________________________________________<br class="">Scip mailing list<br class=""><a href="mailto:Scip@zib.de" class="">Scip@zib.de</a><br class="">https://listserv.zib.de/mailman/listinfo/scip<br class=""></div></blockquote></div><br class=""></div></body></html>