ScoreDirector.getCalculateCount() will tell you the number of moves that have been evaluated (because calculateScore() gets called for every move). MoveSelector.getSize() will tell you the number of possible moves for each step (but only a subset of those are evaluated) To get either of those, you'll need to cast Solver to it's implementation and get hold of the SolverScope. What do you intent to do with it? On 28-02-14 11:11, maciekpob wrote:

On 28-02-14 16:57, maciekpob wrote: Depends on Selector cacheType and selectionOrder (random vs shuffled). See docs, chapter about selectors, cacheType etc. MoveSelector is phase specific, so it's on the SolverPhase. Once again, what are you trying to accomplish? Distinct move selection?

Hey, To debug it, set a breakpoint in LocalSearchDecider. To get it in code: solverPhase = ((DefaultSolver) solver).getSolverPhaseList().get(1); ((DefaultLocalSearchSolverPhase) solverPhase).getDecider().getMoveSelector(); But getDecider() isn't there... (going to add it now for 6.1). HTH somewhat at least On 05-03-14 12:28, maciekpob wrote: