Class NoChangeMove<Solution_>
- Type Parameters:
Solution_- the solution type, the class with thePlanningSolutionannotation
- All Implemented Interfaces:
Move<Solution_>
-
Field Summary
Fields -
Method Summary
Modifier and TypeMethodDescriptionvoidexecute(MutableSolutionView<Solution_> solutionView) Runs the move and optionally records the changes done, so that they can be undone later.Collection<?>Returns all planning entities that this move is changing.Collection<?>Returns all planning values that this move is assigning to entity variables.static <Solution_>
NoChangeMove<Solution_>Rebases a move from an originScoreDirectorto another destinationScoreDirectorwhich is usually on anotherThread.toString()The solver will make sure to only call this when the move is actually printed out during debug logging.
-
Field Details
-
INSTANCE
-
-
Method Details
-
getInstance
-
execute
Description copied from interface:MoveRuns the move and optionally records the changes done, so that they can be undone later. -
rebase
Description copied from interface:MoveRebases a move from an originScoreDirectorto another destinationScoreDirectorwhich is usually on anotherThread. It is necessary for multithreaded solving to function.The new move returned by this method translates the entities and problem facts to the destination
PlanningSolutionof 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.An implementation of this method typically iterates through every entity and fact instance in this move, translates each one to the destination
ScoreDirectorwithRebaser.rebase(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.
-
extractPlanningEntities
Description copied from interface:MoveReturns all planning entities that this move is changing. Required for entity tabu.This method is only called after
Move.execute(MutableSolutionView), 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:
extractPlanningEntitiesin interfaceMove<Solution_>- Returns:
- Each entity only once.
-
extractPlanningValues
Description copied from interface:MoveReturns all planning values that this move is assigning to entity variables. Required for value tabu.This method is only called after
Move.execute(MutableSolutionView), 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:
extractPlanningValuesin interfaceMove<Solution_>- Returns:
- Each value only once.
-
toString
Description copied from interface:MoveThe solver will make sure to only call this when the move is actually printed out during debug logging.
-