Yes, that's correct.
First, posting propagators in commit is okay, no problem.
Second, check "staged propagation" in the following paper:
http://web.it.kth.se/~schulte/paper.html?id=SchulteStuckey:CCoR:2006
Maybe this could be interesting (staging is used extensively in Gecode).
Christian
--
Christian Schulte, http://www.imit.kth.se/~schulte/
-----Original Message-----
From: Luis Quesada [mailto:[EMAIL PROTECTED]
Sent: Tuesday, May 29, 2007 1:27 PM
To: Sébastien Mouthuy
Cc: [EMAIL PROTECTED]; 'Guido Tack'; [EMAIL PROTECTED]
Subject: Re: [gecode-users] order in calls to status and commit...
Sébastien Mouthuy wrote:
> I have another question: posting propagators in the commit function of
> one Branching is acceptable ? The fact is that I would like to delay a
> heavy propagator taht does not do a lot of pruning high in the search
> tree, but is very useful down in the tree.
>
Could you please explain why this cannot be done by the propagator
itself? I think that the propagator can decide whether doing the
expensive pruning or not based on the the current domains of the variables.
Cheers, Luis
_______________________________________________
Gecode users mailing list
[EMAIL PROTECTED]
https://www.gecode.org/mailman/listinfo/gecode-users
