Solution_ - the solution type, the class with the PlanningSolution annotationpublic final class PartitionChangeMove<Solution_> extends AbstractMove<Solution_>
| Constructor and Description |
|---|
PartitionChangeMove(Map<GenuineVariableDescriptor<Solution_>,List<org.apache.commons.lang3.tuple.Pair<Object,Object>>> changeMap,
int partIndex) |
| Modifier and Type | Method and Description |
|---|---|
static <Solution_> |
createMove(InnerScoreDirector<Solution_> scoreDirector,
int partIndex) |
protected PartitionChangeMove<Solution_> |
createUndoMove(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)
Like
AbstractMove.doMove(ScoreDirector) but without the ScoreDirector.triggerVariableListeners() call
(because AbstractMove.doMove(ScoreDirector) already does that). |
Collection<? extends Object> |
getPlanningEntities()
Returns all planning entities that are being changed by this move.
|
Collection<? extends Object> |
getPlanningValues()
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.
|
PartitionChangeMove<Solution_> |
rebase(ScoreDirector<Solution_> destinationScoreDirector)
Rebases a move from an origin
ScoreDirector to another destination ScoreDirector
which is usually on another Thread or JVM. |
String |
toString() |
doMove, rebaseArray, rebaseListclone, equals, finalize, getClass, hashCode, notify, notifyAll, wait, wait, waitgetSimpleMoveTypeDescriptionpublic static <Solution_> PartitionChangeMove<Solution_> createMove(InnerScoreDirector<Solution_> scoreDirector, int partIndex)
protected void doMoveOnGenuineVariables(ScoreDirector<Solution_> scoreDirector)
AbstractMoveAbstractMove.doMove(ScoreDirector) but without the ScoreDirector.triggerVariableListeners() call
(because AbstractMove.doMove(ScoreDirector) already does that).doMoveOnGenuineVariables in class AbstractMove<Solution_>scoreDirector - never nullpublic boolean isMoveDoable(ScoreDirector<Solution_> scoreDirector)
MovePlanningSolution.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
or MoveListFactory, this is not needed as the Solver will do it for you.
scoreDirector - the ScoreDirector not yet modified by the move.protected PartitionChangeMove<Solution_> createUndoMove(ScoreDirector<Solution_> scoreDirector)
AbstractMovecreateUndoMove in class AbstractMove<Solution_>scoreDirector - the ScoreDirector not yet modified by the move.public PartitionChangeMove<Solution_> rebase(ScoreDirector<Solution_> destinationScoreDirector)
MoveScoreDirector to another destination ScoreDirector
which is usually on another Thread or JVM.
The new move returned by this method translates the entities and problem facts
to the destination PlanningSolution of the destination ScoreDirector,
That destination PlanningSolution is a deep planning clone (or an even deeper clone)
of the origin PlanningSolution 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 destination PlanningSolution was in the same state
as the original PlanningSolution 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 with ScoreDirector.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 original PlanningSolution.
So, rebasing can only depend on the identity of planning entities and planning facts,
which is usually declared by a PlanningId on those classes.
It must not depend on the state of the planning variables.
One thread might rebase a move before, amid or after another thread does that same move instance.
This method is thread-safe.
destinationScoreDirector - never null, the ScoreDirector.getWorkingSolution()
that the new move should change the planning entity instances of.public Collection<? extends Object> getPlanningEntities()
MoveAcceptorType.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 returned Collection is recommended to be in a stable order.
For example: use List or LinkedHashSet, but not HashSet.
public Collection<? extends Object> getPlanningValues()
MoveAcceptorType.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 returned Collection is recommended to be in a stable order.
For example: use List or LinkedHashSet, but not HashSet.
Copyright © 2006–2020 JBoss by Red Hat. All rights reserved.