Filip Konvička wrote:
Yes, I think I understand what a branching is in Gecode. The
non-determinism I was interested in was a "choice"-like construct. I
assumed that I could achieve that by posting a cascade of
branchings. I
thought I could install a new branching inside the preceding
branching's
commit function - so during batch recomputation, when only "b)" would
occur, I would get all the branchings I need in a specific search
tree node.
Now I understand what you're up to :-) As a matter of fact, that's
possible. Or rather, it will be in the next release, which fixes a
nasty bug related to "nested" branchings (see the previous thread
"order in calls to status and commit" on this mailing list) .
I looked at some of the examples and I don't remember seeing one that
would use more than one branching. That's why I'm asking these
questions.
Right, in particular, we don't have an example that uses nested
branchings.
As for the library itself, I very much like the design, the language
used and the focus on efficiency. I know that your're probably working
hard on getting version 2 out soon, nevertheless I hope that you
publish
some brief tutorial for newbies like me sometime soon :-)
This is still high on our agenda, but we can't make promises about a
release date for the tutorial at the moment.
Cheers,
Guido
--
Guido Tack
Programming Systems Lab, Saarland University, Germany
http://www.ps.uni-sb.de/~tack
_______________________________________________
Gecode users mailing list
[EMAIL PROTECTED]
https://www.gecode.org/mailman/listinfo/gecode-users
