Hi,
@David: nifty idea, never thought of that.
There are several possibilities here of how we could help:
- Merge Groups in the release version: here you get a lot of control over
how propagators are executed, the idea you can find here:
http://web.it.kth.se/~cschulte/paper.php?id=LagerkvistSchulte:CP:2009
We thought whether this should be part of Gecode 4 (which will be released
tomorrow, most likely) but decided against it as we do not have any killer
applications right now.
- Make Gecode's testing infrastructure accessible (documentation, make
available as library). The testing infrastructure is very powerful and we
know from experience that if the tests are well-designed you hardly ever
miss a bug in a propagator.
Would any of this help? Both are quite some work and we are really exhausted
after Gecode 4 (the new features are cool, though).
Christian
--
Christian Schulte, www.ict.kth.se/~cschulte/
> -----Original Message-----
> From: users-boun...@gecode.org [mailto:users-boun...@gecode.org] On
> Behalf Of David Rijsman
> Sent: Wednesday, March 13, 2013 6:11 PM
> To: users@gecode.org; Dirk Schnorpfeil
> Subject: Re: [gecode-users] Getting ID of actor failing a space
>
> Hi Dirk,
>
> if you still have access to the propagators you could check if the
accumulated
> failure count has increased, you will have to know what it was before you
> started propagation off course. For the propagators you wrote yourself you
> could (un)register them to your space as (being done) propagating and then
you
> at least know if that one created the failure directly. As you already
indicated it
> will only tell you who was the lucky propagator to conclude failure,
>
>
>
>
>
> 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.rijs...@quintiq.com
> I www.quintiq.com
>
>
> >>>
> From: Dirk Schnorpfeil <d.schnorpf...@web.de>
> To: <users@gecode.org>
> Date: 13-3-2013 17:40
> Subject: [gecode-users] Getting ID of actor failing a space
>
> Hi folks!
>
> First let me introduce myself to the list:
> I am a software developer for scheduling and planning systems working for
a
> small company in germany. As i love gecode i put it into the heart of the
> scheduling system i am currently working on. From the use of gecode the
> following question came up to me:
>
>
> When using gecode in practice with large models (many many constraints) it
is
> sometimes hard to find out why a space is failed. This comes esp. true
when you
> implement new propagators or branchers and when you debug them (they dont
> fail the space but because of a bug in the newly added propagator another
> constraint failes...)
>
> I often wished a functionality that lets me tag all actors (propagators,
> branchers) with an ID while posting them and when a space is failed i
could
> simply by retrieving that ID (of last executed actor) get some idea which
> constraint failed the space.
>
> Is there some functionality or is there even a better way to do this?
>
> Many thanks in advance!
>
> Dirk
>
>
> _______________________________________________
> Gecode users mailing list
> users@gecode.org
> https://www.gecode.org/mailman/listinfo/gecode-users
>
>
>
> _______________________________________________
> Gecode users mailing list
> users@gecode.org
> https://www.gecode.org/mailman/listinfo/gecode-users
_______________________________________________
Gecode users mailing list
users@gecode.org
https://www.gecode.org/mailman/listinfo/gecode-users
