[Scip] Question about branching on master variables in SCIP

Chiwei Yan chiwei at mit.edu
Fri Aug 7 16:38:07 CEST 2015


Hi Yongjia,

    Sorry for jumping into the discussion. Got interested in this thread. Maybe I am completely wrong, but it seems to me that if you only do variable branching instead of some fancy constraint branching (say Ryan/Foster), the original pricing routine should still work even after the branching? Basically you fix a variable in the restricted master formulation, and this will automatically change the dual information. I am not sure how SCIP implement the branching rule, but if it is simply adding a constraint to the master problem on every new B&B node, maybe the original pricer should still work.

    Sorry for interrupting your discussion.

Best,
Chiwei
________________________________
From: Scip [scip-bounces at zib.de] on behalf of Yongjia Song [ysong3 at vcu.edu]
Sent: Friday, August 07, 2015 10:02 AM
To: Benjamin Müller; SCIP mailing list
Subject: Re: [Scip] Question about branching on master variables in SCIP

Hi Benny,

Thanks a lot! I actually tried a set partitioning formulation with only master variables, and claim them to be integer so branching has to be done for these variables. I only specify a pricer as the one in the VRP example. Will Scip automatically take care of the extra complication in pricing because of branching? I actually tried this, and sometimes it gave the correct solution(maybe out of luck) but it also happened that no progress is made at all after the root. Any explanation on this? Thanks a lot!

Best,
________________________________
From: Benjamin Müller<mailto:benjamin.mueller at zib.de>
Sent: ‎8/‎7/‎2015 3:50 AM
To: Yongjia Song<mailto:ysong3 at vcu.edu>; SCIP mailing list<mailto:scip at zib.de>
Subject: Re: [Scip]  Question about branching on master variables in SCIP

Hi Yongjia,

you are completely right, branching on the reformulated variables does change the nature of your pricing problem. If your model does only contain the routing variables and you declare them as integral then SCIP will branch on those as SCIP would usually do. The user has to respect the branching decisions made by SCIP in his pricer. You could add your own branching rule in order to branch on the original variables even though they are not in the model (see Ryan/Foster branching in the Binpacking example).

Note that, in the VRP example the routine variables are continuous and thus branching will only be applied on edge variables. Those branching decisions does not influence the pricing problem too much (excluding edges from the graph).


Best,

Benny


On 08/06/2015 08:01 PM, Yongjia Song wrote:
Hi all,

I have a question about how SCIP handles branching when only the master variables present in the model. Taking VRP as an example, suppose we only have the route variables (without the original edge variables or the linking constraints between edge variables and route variables), and we impose the integrality constraints on these variables, it is not clear how branching on these variables are implemented in SCIP. Indeed, when a branching decision is made on some route variable, it complicates the pricing by forcing the pricing algorithm to avoid generating that route. Without specific problem structure, it is not clear to me how SCIP handles this case. Thanks a lot for your help!

Best,

--
SONG, Yongjia
Assistant Professor
Department of Statistical Sciences and Operations Research
Virginia Commonwealth University
PO Box 843083
Richmond, VA 23284-3083
804-828-1149
Ysong3 at vcu.edu<mailto:Ysong3 at vcu.edu>



_______________________________________________
Scip mailing list
Scip at zib.de<mailto:Scip at zib.de>
http://listserv.zib.de/mailman/listinfo/scip



--
______________________________
Benjamin Müller
Zuse Institute Berlin
Takustr. 7, 14195 Berlin
benjamin.mueller at zib.de<mailto:benjamin.mueller at zib.de>
+49 30 841 85-195
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://listserv.zib.de/pipermail/scip/attachments/20150807/4e441740/attachment.html>


More information about the Scip mailing list