Re: [rules-users] Planner: Hard Constraint Prevents Moves and Swaps

Op 27-09-12 19:28, jrvirtue schreef: I usually mix both: <unionMoveSelector> <changeMoveSelector/> <swapMoveSelector/> <pillarSwapMoveSelector/> </unionMoveSelector> Just try it out and use the benchmarker to find the best set for your use case. You mean you have multiple planning vars, but only want to pillarSwap to base on and affect 1 var (and ignore the other vars)? The PillarSwapMoveSelectorConfig class doesn't support that yet, but the PillarSwapMoveSelector class itself does. Currently the PillarSwapMoveSelectorConfig always pillarSwaps around all vars: public MoveSelector buildBaseMoveSelector(EnvironmentMode environmentMode, SolutionDescriptor solutionDescriptor, SelectionCacheType minimumCacheType, SelectionOrder resolvedSelectionOrder) { ... Collection<PlanningVariableDescriptor> variableDescriptors = leftPillarSelector.getEntityDescriptor() .getPlanningVariableDescriptors(); // This should be a singleton of just the variable you want return new PillarSwapMoveSelector(leftPillarSelector, rightPillarSelector, variableDescriptors, resolvedSelectionOrder == SelectionOrder.RANDOM); } That class really needs something like this: @XStreamImplicit(itemFieldName = "swapPlanningVariable") private List<String> swapPlanningVariableList = null; so you can do <pillarSwapMoveSelector> <swapPlanningVariable>timeSlot</swapPlanningVariable> </pillarSwapMoveSelector> Same story for SwapMoveSelectorConfig. Pull requests welcome :)