[Scip] Upper bound on variables during pricing

[Gerald Gamrath]

Hi Hélène,

you are right, that should not happen. Can you send me the solving
statistics, which you get by typing "display statistics" in the
interactive shell or calling SCIPprintStatistics()? This should help to
identify the plugin which changes the bound.

Besides, you best disable the other propagators, too, if you don't want
SCIP to change bounds itself. You can either disable all propagation by
setting propagating/maxrounds and propagating/maxroundsroot to 0, but I
guess your modifications to the problem data after branching are also
done during propagation? In this case, you need to disable all default
propagators individually by setting their freqency to -1.

Best,
Gerald

Am 18.03.2013 11:37, schrieb Hélène Toussaint:
>
> Dear all,
>
> I use SCIP to code a branch & price algorithm on positive continuous
> variables. I branch on instance data (using a constraint handler to
> store the branching decisions). When I modify the instance data some
> variables become forbidden (I fix their upper bound to 0).
>
>  
>
> I'd like SCIP to not set upper bound on the other variables. As
> explained in the FAQ I have marked all constraints containing priced
> variables as modifiable and added SCIPsetIntParam(scip,
> "propagating/rootredcost/freq", -1). But occasionally there is a
> variable with an upper bound equals to 0 although it isn't forbidden
> in the current node. How is this possible? Could you please help me
> with this issue?
>
>  
>
> Best regards,
>
> Hélène
>
>
>
> _______________________________________________
> Scip mailing list
> Scip at zib.de
> http://listserv.zib.de/mailman/listinfo/scip

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://listserv.zib.de/mailman/private/scip/attachments/20130319/3e987d17/attachment.html