Actually, I have to say that this is not that easy: failure might actually not be due to the propagator run last. It could be due to a variable modified outside a propagator (when posting constraint or using a branching).
Moreover, the propagator run last is typically not the culprit of things going wrong. Cheers Christian -- Christian Schulte, www.ict.kth.se/~cschulte/ -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Mikael Zayenz Lagerkvist Sent: Thursday, March 27, 2008 3:27 PM To: David Rijsman Cc: [EMAIL PROTECTED] Subject: Re: [gecode-users] Access to the last propagator invoked in case of ES_FAILED Hi, There is no way currently to access this information, and no current plans to introduce it. However, it would not be hard to implement yourself. As a starting-point, see the implementation of the function Space::status in gecode/kernel/core.cc. What is it that you want to do with this information? Since propagators do not have any identifier that is stable between copies, the information seems to me to be of little use. Cheers, Mikael On Thu, Mar 27, 2008 at 3:03 PM, David Rijsman <[EMAIL PROTECTED]> wrote: > I would like to know if it is possible to determine the last propator > invoked in case Space::status returns ES_FAILED or if there are any > plans to expose this information. If one can get this information (in > the future) will one also introduce reflection API on the Propagator > level? > > David Rijsman > > _______________________________________________ > Gecode users mailing list > [EMAIL PROTECTED] > https://www.gecode.org/mailman/listinfo/gecode-users > -- Mikael Zayenz Lagerkvist, http://www.ict.kth.se/~zayenz/ _______________________________________________ Gecode users mailing list [EMAIL PROTECTED] https://www.gecode.org/mailman/listinfo/gecode-users _______________________________________________ Gecode users mailing list [EMAIL PROTECTED] https://www.gecode.org/mailman/listinfo/gecode-users
