[gecode-users] order in calls to status and commit...

[Sébastien Mouthuy]

I also post some propagators inside the commit function. Is it ok ? I am
sure these propagators cannot fail when posting. 

When I post propagators *and* branching in the same commit, I have the
problem I described before.

When I post branching *xor* propagators, the branching posted clones
forever at some point.

When I don't put any propagators inside commit, but in the constructor
of my space, the problem seems to disappear, but I am not sure.

Thanks for any help,

bye bye,

sebastien 

UCL

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
> 
> 
> 
> 
>