Op 05-02-13 04:25, john poole schreef: > Thanks. If the "Best score over time" line doesn't flatline, does that mean > it needs more time or that the configuration isn't ever going to produce a > good solution? Define "good" solution :) - Close to optimal: impossible to know the optimal for most realistic problems (and extrapolating quality from easier, smaller problems is broken) - Better than other algorithms: that's why planner has the benchmarker.
My advice is to use the benchmarker and configure different algo's (see the examples *SolverBenchmark.xml) and a distinct set of datasets. Then a bad solution should stick out like a sore thumb in the benchmark report. > > > -- > View this message in context: > http://drools.46999.n3.nabble.com/Found-solution-vs-actual-optimum-tp4022027p4022053.html > Sent from the Drools: User forum mailing list archive at Nabble.com. > _______________________________________________ > rules-users mailing list > [email protected] > https://lists.jboss.org/mailman/listinfo/rules-users > _______________________________________________ rules-users mailing list [email protected] https://lists.jboss.org/mailman/listinfo/rules-users
