I found a related problem that seems annoying. I have one main branching, let's say BrSF. In the commit function of BrSF, I sometimes post another branching, say BrCl.
I printed id's of these branching and it happens that an instance of BrSF has the same id as BrCl. I'm not using recomputation: c_d = 1, a_d = 10000. The problem then is that the search engine calls the commit function of the BrSF with a description returned by an instance of BrCL. and this is very annoying :). It is perhaps this same problem that leads to the NoBranching exception when using recomputation. any idea ? It would be very useful for me. Thank you. seb Le lundi 28 mai 2007 à 20:46 +0200, Guido Tack a écrit : > Sébastien Mouthuy wrote: > > > > Could that be the problem ? Should B1 and B2 be two copies of a > > comman > > instance of the branching ? I know descriptions and branchings use > > id's. > > could it be the problem ? > > > Hm, it shouldn't be the problem. If the branchings are always created > in the same order, the ids will be the same. Could you verify this? > Just print the id in the Branching constructor, and check that it's > the same no matter whether you use recomputation or not. > > > The one thing we do not support is creating a branching in a > propagator. This won't work because propagation order can be different > during recomputation, so the creation order of the branchings would be > different and the ids would not match. > > > Cheers, > Guido > > -- > Guido Tack > Programming Systems Lab, Saarland University, Germany > http://www.ps.uni-sb.de/~tack > > > > > _______________________________________________ Gecode users mailing list [EMAIL PROTECTED] https://www.gecode.org/mailman/listinfo/gecode-users
