I don't remember if I do this or not - so this is just a reminder to check on this.
When columns are leftover in the column pool (possibly from other tree nodes), they need to be scanned to see if they satisfy the branching decisions before considering entering them. We might just sort based on updated reduced costs and then allow them to enter - which could lead to an error when branching in subprobs and inefficiency when branching in master.
Issue created by migration from Trac.
Original creator: @mgalati13
Original creation time: 2011-12-08 19:06:26
Assignee: @mgalati13
I don't remember if I do this or not - so this is just a reminder to check on this.
When columns are leftover in the column pool (possibly from other tree nodes), they need to be scanned to see if they satisfy the branching decisions before considering entering them. We might just sort based on updated reduced costs and then allow them to enter - which could lead to an error when branching in subprobs and inefficiency when branching in master.