Class AbstractUndoMove<Solution_>
- Type Parameters:
Solution_- the solution type, the class with thePlanningSolutionannotation
- All Implemented Interfaces:
Move<Solution_>
- Direct Known Subclasses:
ListRuinRecreateUndoMove,RecordedUndoMove,RuinRecreateUndoMove,UndoKOptListMove
Move, suggested starting point to implement undo moves
when not using AbstractSimplifiedMove.
Unless raw performance is a concern, consider using AbstractSimplifiedMove instead.- See Also:
-
Field Summary
Fields -
Constructor Summary
Constructors -
Method Summary
Modifier and TypeMethodDescriptiondoMove(ScoreDirector<Solution_> scoreDirector) Does the move (which indirectly affects theScoreDirector.getWorkingSolution()).protected abstract voiddoMoveOnGenuineVariables(ScoreDirector<Solution_> scoreDirector) LikedoMoveOnly(ScoreDirector)but without theScoreDirector.triggerVariableListeners()call (becausedoMoveOnly(ScoreDirector)already does that).final voiddoMoveOnly(ScoreDirector<Solution_> scoreDirector) As defined byMove.doMove(ScoreDirector), but does not return an undo move.final Collection<?>Returns all planning entities that are being changed by this move.final Collection<?>Returns all planning values that entities are being assigned to by this move.Describes the move type for statistical purposes.final booleanisMoveDoable(ScoreDirector<Solution_> scoreDirector) Called before a move is evaluated to decide whether the move can be done and evaluated.toString()
-
Field Details
-
parentMove
-
-
Constructor Details
-
AbstractUndoMove
-
-
Method Details
-
isMoveDoable
Description copied from interface:MoveCalled before a move is evaluated to decide whether the move can be done and evaluated. A Move is not doable if:- Either doing it would change nothing in the
PlanningSolution. - Either it's simply not possible to do (for example due to built-in hard constraints).
It is recommended to keep this method implementation simple: do not use it in an attempt to satisfy normal hard and soft constraints.
Although you could also filter out non-doable moves in for example the
MoveSelectororMoveListFactory, this is not needed as theSolverwill do it for you.- Specified by:
isMoveDoablein interfaceMove<Solution_>- Parameters:
scoreDirector- theScoreDirectornot yet modified by the move.- Returns:
- true if the move achieves a change in the solution and the move is possible to do on the solution.
- Either doing it would change nothing in the
-
doMove
Description copied from interface:MoveDoes the move (which indirectly affects theScoreDirector.getWorkingSolution()). When theworking solutionis modified, theScoreDirectormust be correctly notified (throughScoreDirector.beforeVariableChanged(Object, String)andScoreDirector.afterVariableChanged(Object, String)), otherwise later calculatedScores will be corrupted.This method must end with calling
ScoreDirector.triggerVariableListeners()to ensure all shadow variables are updated.This method must return an undo move, so the move can be evaluated and then be undone without resulting into a permanent change in the solution.
- Specified by:
doMovein interfaceMove<Solution_>- Parameters:
scoreDirector- never null, theScoreDirectorthat needs to get notified of the changes- Returns:
- an undoMove which does the exact opposite of this move
-
doMoveOnly
Description copied from interface:MoveAs defined byMove.doMove(ScoreDirector), but does not return an undo move.- Specified by:
doMoveOnlyin interfaceMove<Solution_>- Parameters:
scoreDirector- never null, theScoreDirectorthat needs to get notified of the changes
-
doMoveOnGenuineVariables
LikedoMoveOnly(ScoreDirector)but without theScoreDirector.triggerVariableListeners()call (becausedoMoveOnly(ScoreDirector)already does that).- Parameters:
scoreDirector- never null
-
getPlanningEntities
Description copied from interface:MoveReturns all planning entities that are being changed by this move. Required forAcceptorType.ENTITY_TABU.This method is only called after
Move.doMove(ScoreDirector)(which might affect the return values).Duplicate entries in the returned
Collectionare best avoided. The returnedCollectionis recommended to be in a stable order. For example: useListorLinkedHashSet, but notHashSet.- Specified by:
getPlanningEntitiesin interfaceMove<Solution_>- Returns:
- never null
-
getPlanningValues
Description copied from interface:MoveReturns all planning values that entities are being assigned to by this move. Required forAcceptorType.VALUE_TABU.This method is only called after
Move.doMove(ScoreDirector)(which might affect the return values).Duplicate entries in the returned
Collectionare best avoided. The returnedCollectionis recommended to be in a stable order. For example: useListorLinkedHashSet, but notHashSet.- Specified by:
getPlanningValuesin interfaceMove<Solution_>- Returns:
- never null
-
getSimpleMoveTypeDescription
Description copied from interface:MoveDescribes the move type for statistical purposes. For example "ChangeMove(Process.computer)".The format is not formalized. Never parse the
Stringreturned by this method.- Specified by:
getSimpleMoveTypeDescriptionin interfaceMove<Solution_>- Returns:
- never null
-
toString
-