[gecode-users] Branching decision updates an existing propagator

[Christian Schulte]

Hi David,

Funny, we added support for this some time ago (also for temporal networks
;-)) but we never made it round to implement the networks (still on our todo
list).

The best way to do it is to create a local object with a local handle that
can be shared among several propagators/and or branchers. This is described
in Section 27.4 in MPG. Then the propagator can add the information to this
shared object and the brancher can read from there.

Hope that helps.

Best
Christian


--
Christian Schulte, www.ict.kth.se/~cschulte/


-----Original Message-----
From: users-bounces at gecode.org [mailto:users-bounces at gecode.org] On Behalf
Of David Rijsman
Sent: Tuesday, February 12, 2013 4:22 PM
To: users at gecode.org
Subject: [gecode-users] Branching decision updates an existing propagator

Hi All,

I am wondering if there is pattern to be used if I have a propagator which
can be fed with new information by a branching decision.  Specifically I
have a temporal propagator maintaining a temporal network and if a branch
decision is to introduce a new precedence relation (ordering between two
views present in the network) I would like to forward this information to
the temporal propagator. 

I was thinking of maintaining a unary relation to my temporal propagator in
my extended space, this relation might become null when the propagator is
subsumed. I also need to introduce a post precedence constraint API on my
extended space which notifies to temporal propagator of the new precedence
constraint. This API on the space can then be invoked by the brancher.

Would this be the best way of doing something like this? 



David J. Rijsman
Algorithm Lead
Quintiq
 
T +31 (0)73 691 07 39
F +31 (0)73 691 07 54
M +31 (0)62 127 68 29
E david.rijsman at quintiq.com
I www.quintiq.com



_______________________________________________
Gecode users mailing list
users at gecode.org
https://www.gecode.org/mailman/listinfo/gecode-users