Class ChainedSwapMove<Solution_>
- Type Parameters:
Solution_- the solution type, the class with thePlanningSolutionannotation
- All Implemented Interfaces:
Move<Solution_>
-
Field Summary
FieldsModifier and TypeFieldDescriptionFields inherited from class ai.timefold.solver.core.impl.heuristic.selector.move.generic.SwapMove
leftEntity, rightEntity, variableDescriptorList -
Constructor Summary
ConstructorsConstructorDescriptionChainedSwapMove(List<GenuineVariableDescriptor<Solution_>> genuineVariableDescriptors, Object leftEntity, Object rightEntity, List<Object> oldLeftTrailingEntityList, List<Object> oldRightTrailingEntityList) ChainedSwapMove(List<GenuineVariableDescriptor<Solution_>> variableDescriptorList, List<SingletonInverseVariableSupply> inverseVariableSupplyList, Object leftEntity, Object rightEntity) -
Method Summary
Modifier and TypeMethodDescriptioncreateUndoMove(ScoreDirector<Solution_> scoreDirector) Called before the move is done, so the move can be evaluated and then be undone without resulting into a permanent change in the solution.protected voiddoMoveOnGenuineVariables(ScoreDirector<Solution_> scoreDirector) LikeAbstractMove.doMoveOnly(ScoreDirector)but without theScoreDirector.triggerVariableListeners()call (becauseAbstractMove.doMoveOnly(ScoreDirector)already does that).rebase(ScoreDirector<Solution_> destinationScoreDirector) Rebases a move from an originScoreDirectorto another destinationScoreDirectorwhich is usually on anotherThreador JVM.Methods inherited from class ai.timefold.solver.core.impl.heuristic.selector.move.generic.SwapMove
appendVariablesToString, equals, getLeftEntity, getPlanningEntities, getPlanningValues, getRightEntity, getSimpleMoveTypeDescription, hashCode, isMoveDoable, toStringMethods inherited from class ai.timefold.solver.core.impl.heuristic.move.AbstractMove
doMove, doMoveOnly, rebaseList, rebaseSet
-
Field Details
-
oldLeftTrailingEntityList
-
oldRightTrailingEntityList
-
-
Constructor Details
-
ChainedSwapMove
public ChainedSwapMove(List<GenuineVariableDescriptor<Solution_>> variableDescriptorList, List<SingletonInverseVariableSupply> inverseVariableSupplyList, Object leftEntity, Object rightEntity) -
ChainedSwapMove
-
-
Method Details
-
createUndoMove
Description copied from class:AbstractMoveCalled before the move is done, so the move can be evaluated and then be undone without resulting into a permanent change in the solution.- Overrides:
createUndoMovein classSwapMove<Solution_>- Parameters:
scoreDirector- theScoreDirectornot yet modified by the move.- Returns:
- an undoMove which does the exact opposite of this move.
-
doMoveOnGenuineVariables
Description copied from class:AbstractMoveLikeAbstractMove.doMoveOnly(ScoreDirector)but without theScoreDirector.triggerVariableListeners()call (becauseAbstractMove.doMoveOnly(ScoreDirector)already does that).- Overrides:
doMoveOnGenuineVariablesin classSwapMove<Solution_>- Parameters:
scoreDirector- never null
-
rebase
Description copied from interface:MoveRebases a move from an originScoreDirectorto another destinationScoreDirectorwhich is usually on anotherThreador JVM. The new move returned by this method translates the entities and problem facts to the destinationPlanningSolutionof the destinationScoreDirector, That destinationPlanningSolutionis a deep planning clone (or an even deeper clone) of the originPlanningSolutionthat this move has been generated from.That new move does the exact same change as this move, resulting in the same
PlanningSolutionstate, presuming that destinationPlanningSolutionwas in the same state as the originalPlanningSolutionto begin with.Generally speaking, an implementation of this method iterates through every entity and fact instance in this move, translates each one to the destination
ScoreDirectorwithScoreDirector.lookUpWorkingObject(Object)and creates a new move instance of the same move type, using those translated instances.The destination
PlanningSolutioncan be in a different state than the originalPlanningSolution. So, rebasing can only depend on the identity ofplanning entitiesandproblem facts, which are usually declared by aPlanningIdon those classes. It must not depend on the state of theplanning variables. One thread might rebase a move before, amid or after another thread does that same move instance.This method is thread-safe.
- Specified by:
rebasein interfaceMove<Solution_>- Overrides:
rebasein classSwapMove<Solution_>- Parameters:
destinationScoreDirector- never null, theScoreDirector.getWorkingSolution()that the new move should change the planning entity instances of.- Returns:
- never null, a new move that does the same change as this move on another solution instance
-