Class NoChangeMove<Solution_>
- Type Parameters:
Solution_
- the solution type, the class with thePlanningSolution
annotation
- All Implemented Interfaces:
Move<Solution_>
-
Constructor Summary
-
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 void
doMoveOnGenuineVariables
(ScoreDirector<Solution_> scoreDirector) LikeAbstractMove.doMoveOnly(ScoreDirector)
but without theScoreDirector.triggerVariableListeners()
call (becauseAbstractMove.doMoveOnly(ScoreDirector)
already does that).Collection<? extends Object>
Returns all planning entities that are being changed by this move.Collection<? extends Object>
Returns all planning values that entities are being assigned to by this move.boolean
isMoveDoable
(ScoreDirector<Solution_> scoreDirector) Called before a move is evaluated to decide whether the move can be done and evaluated.rebase
(ScoreDirector<Solution_> destinationScoreDirector) Rebases a move from an originScoreDirector
to another destinationScoreDirector
which is usually on anotherThread
or JVM.toString()
Methods inherited from class org.optaplanner.core.impl.heuristic.move.AbstractMove
doMove, doMoveOnly, rebaseArray, rebaseList
Methods inherited from class java.lang.Object
clone, equals, finalize, getClass, hashCode, notify, notifyAll, wait, wait, wait
Methods inherited from interface org.optaplanner.core.impl.heuristic.move.Move
getSimpleMoveTypeDescription
-
Constructor Details
-
NoChangeMove
public NoChangeMove()
-
-
Method Details
-
isMoveDoable
Description copied from interface:Move
Called 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
MoveSelector
orMoveListFactory
, this is not needed as theSolver
will do it for you.- Parameters:
scoreDirector
- theScoreDirector
not 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
-
createUndoMove
Description copied from class:AbstractMove
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.- Specified by:
createUndoMove
in classAbstractMove<Solution_>
- Parameters:
scoreDirector
- theScoreDirector
not yet modified by the move.- Returns:
- an undoMove which does the exact opposite of this move.
-
doMoveOnGenuineVariables
Description copied from class:AbstractMove
LikeAbstractMove.doMoveOnly(ScoreDirector)
but without theScoreDirector.triggerVariableListeners()
call (becauseAbstractMove.doMoveOnly(ScoreDirector)
already does that).- Specified by:
doMoveOnGenuineVariables
in classAbstractMove<Solution_>
- Parameters:
scoreDirector
- never null
-
rebase
Description copied from interface:Move
Rebases a move from an originScoreDirector
to another destinationScoreDirector
which is usually on anotherThread
or JVM. The new move returned by this method translates the entities and problem facts to the destinationPlanningSolution
of the destinationScoreDirector
, That destinationPlanningSolution
is a deep planning clone (or an even deeper clone) of the originPlanningSolution
that this move has been generated from.That new move does the exact same change as this move, resulting in the same
PlanningSolution
state, presuming that destinationPlanningSolution
was in the same state as the originalPlanningSolution
to 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
ScoreDirector
withScoreDirector.lookUpWorkingObject(Object)
and creates a new move instance of the same move type, using those translated instances.The destination
PlanningSolution
can be in a different state than the originalPlanningSolution
. So, rebasing can only depend on the identity ofplanning entities
and planning facts, which is usually declared by aPlanningId
on 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.
- 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
-
getPlanningEntities
Description copied from interface:Move
Returns 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
Collection
are best avoided. The returnedCollection
is recommended to be in a stable order. For example: useList
orLinkedHashSet
, but notHashSet
.- Returns:
- never null
-
getPlanningValues
Description copied from interface:Move
Returns 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
Collection
are best avoided. The returnedCollection
is recommended to be in a stable order. For example: useList
orLinkedHashSet
, but notHashSet
.- Returns:
- never null
-
toString
-