Hi Tim,
First, the %-done calculation make sense only when you want to find
_all_ solutions instead of a single solution. This is because finding
the first solution, depending upon your heuristics, could take much less
time than searching for all possible solutions.
Supposing you want _all_ solutions: Suppose your problem has 3 variables
A, B, C with domain sizes 2, 3, and 4 respectively, then the total
number of combinations to try for solutions are 2 * 3 * 4 = 24. It is
trivial to customize search script (see Search.oz in Oz distribution) to
keep track of combinations eliminated (= 100% - remaining) using
{FD.reflect.size Var} for all variables and multiplying them. Keep
updating the %-done. However, I must say that it is practical only for
small problems. For real world problems the combinations are just too
many to try them all. Also, for not wasting too much time calculating
%-done, you could update it less often, e.g. after every few seconds or
every time the depth of search tree changes from smaller to greater than
some depth 'X' (better).
-- Himanshu.
-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
On Behalf Of Tim Heath
Sent: Thursday, June 08, 2006 2:46 PM
To: [EMAIL PROTECTED]
Subject: A kind of status bar to see where the Search is in csp
Hi Oz Gurus,
I want to make a kind of status bar showing how the search is going for
csp application. Any ideas how to do that? I know if I look at the
explorer it shows the tree as it is being populated. What I am not
clear on is if there is a way to know if it is like 50% done or 75% done
at any period of time programatically.
Oz rocks!
________________________________________________________________________
_________
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
