[...] when a node is either suspended or failed, you can't set the cursor on such a node.
Before I start experimenting with this, is there a wise reason not to do so?
I don't know the answer, just want to confirm that I would like to know that as well.
Anyway, what I usually do to get information about such a node is comparing the space before, and the next branch. This also works nicely for full subtrees. You can define your own comparison procedure that may traverse your data structure.
Best Torsten On 18.09.2009, at 18:45, Nanitous wrote:
Hi All, Today I've been experimenting a little bit with Gecode and its explorer called Gist. In the Mozart Explorer you can't inspect the a failed solution node. Whereas in Gist you can and it shows the a solution that can't satisfy the constraints. I think this is interesting "constraint debug" information, and it is a pity the Mozart Explorer doesn't even let you activate your own inspector on failed nodes, as you even can't even select such a node. I looked at the Mozart Explorer code, and I found in the the methode SetCursor of the Manager class that when a node is either suspended or failed, you can't set the cursor on such a node. Before I start experimenting with this, is there a wise reason not to do so? I'm looking forward to your views on this. kr Twan _________________________________________________________________________________ mozart-users mailing list [email protected] http://www.mozart-oz.org/mailman/listinfo/mozart-users
_________________________________________________________________________________ mozart-users mailing list [email protected] http://www.mozart-oz.org/mailman/listinfo/mozart-users
