Hi Kish,
To give you some background, there are some crucial differences in how
AFC on one hand and Action and CHB are implemented. The latter two are
properties of individual variables with regards to propagations and
failures during search. They are implemented as AC_RECORD propagators,
which is a special priority level used for propagators that only
record information. AFC (accumulated failure count) is a property of
the summed behaviour of propagators subscribed to a variable - namely,
how many times they have triggered failure. This is not possible to
implement using a recording propagator, as the propagator and it's
advisors only know some of what has happened to a variable, not what
propagator triggered it. Thus, AFC is integrated more closely into the
Gecode architecture.
There is currently no easy way to dynamically extend the Action and
CHB information recorders. I'll think about if there is some good
workaround, but it probably highly depends on what the specific
requirements for your interface are.
Cheers,
Mikael
> --
> You received this message because you are subscribed to the Google Groups "Gecode" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to
gecode+un...@googlegroups.com.
> To view this discussion on the web visit
https://groups.google.com/d/msgid/gecode/CAHM-QAs29gMfdV3vRwve6o9NWESTqQ6skaCcN8mV1BY8V5Urqg%40mail.gmail.com.
--
Mikael Zayenz Lagerkvist