[gecode-users] Diagnosing failures
Malcolm Ryan
malcolmr at cse.unsw.edu.au
Fri Nov 16 00:54:29 CET 2007
On 13/11/2007, at 5:00 PM, Malcolm Ryan wrote:
> On 13/11/2007, at 7:25 AM, Christian Schulte wrote:
>
>> That's not quite an option: well known, there are too many propagator
>> invocations (really, absolutely incomprehensible).
>
> Really? I wouldn't have thought that there were so many. But then
> I've never written an engine.
I've been thinking about this some more and I'd really like to look
into the debugging problem more deeply. I have some ideas I'd like to
play with. When you say "too many propagator invocations", exactly
how many are we talking about? Is there a simple mapping from a
propagator to the constraint that created it? Is there any way I can
access this data?
Malcolm
--
"An inconvenience is only an adventure wrongly considered;
an adventure is an inconvenience rightly considered."
- G.K.Chesterton, On Running After Ones Hat
More information about the gecode-users
mailing list