cusack.hcg.games.pebble.algorithms.solvability.nondeterministic

Class IsSolvableShortestPebblePath

java.lang.Object

cusack.hcg.graph.algorithm.AbstractAlgorithm<PebbleInstance>

cusack.hcg.games.pebble.algorithms.PebbleAlgorithm

cusack.hcg.games.pebble.algorithms.EfficientPebbleAlgorithm

cusack.hcg.games.pebble.algorithms.solvability.nondeterministic.IsSolvableShortestPebblePath

All Implemented Interfaces:

AlgorithmInterface<PebbleInstance>

public class IsSolvableShortestPebblePath
extends EfficientPebbleAlgorithm

Author:

Chuck Cusack, 6/29/16. Based on IsSolvableShortestPath. This version takes into account pebbles on the vertices. The distance from a to b is reduced by the number of vertices on a shortest path that have pebbles. In fact, the actually paths may be much longer in this version, but pebbles are easier to move along them.

Constructor Summary

Constructors

Constructor and Description
IsSolvableShortestPebblePath()

Method Summary

Modifier and Type	Method and Description
java.lang.String	argumentFormat() Describe how the argument(s) to the algorithm should be formatted, if applicable.
boolean	countsOperations()
double	getVersion() Mostly for use in comparing results from previous versions of algorithms, and/or so we can know whether or not data in the database is based on an older version of the algorithm.
void	initializeMoreData() Called by initializeData which is called by setPuzzleData.
void	parseArguments(java.lang.String args) Sends a string that the user can enter to the algorithm.
void	reinitializeMoreData() If resetWithThesePebbles is called, what else needs to be reinitialized before the algorithm can be run? This is supposed to be much more efficient than calling initializeMoreData.
void	runAlgorithm() Runs the Algorithm.

Methods inherited from class cusack.hcg.games.pebble.algorithms.EfficientPebbleAlgorithm

getCovered, getCurrentProblemData, resetWithThesePebbles, resetWithThesePebbles

Methods inherited from class cusack.hcg.games.pebble.algorithms.PebbleAlgorithm

getPebbleState, getProblemType, getProgressReport, getResult, initializeData, quit, setPebbleState

Methods inherited from class cusack.hcg.graph.algorithm.AbstractAlgorithm

getNumberOfOperations, getState, isDone, isNotDone, isQuit, setProblemData, setState

Methods inherited from class java.lang.Object

equals, getClass, hashCode, notify, notifyAll, toString, wait, wait, wait

Constructor Detail

IsSolvableShortestPebblePath

public IsSolvableShortestPebblePath()

Method Detail

runAlgorithm

public void runAlgorithm()

Description copied from interface: AlgorithmInterface

Runs the Algorithm. This is the most important method.

initializeMoreData

public void initializeMoreData()

Description copied from class: PebbleAlgorithm

Called by initializeData which is called by setPuzzleData. It should initialize data in the subclass that needs it.

Overrides:

initializeMoreData in class EfficientPebbleAlgorithm

countsOperations

public boolean countsOperations()

Returns:

True if and only if the algorithm intends to keep track of the number of operations it is performing. Each algorithm is free to decide what it considers an "operation" to be.

getVersion

public double getVersion()

Description copied from interface: AlgorithmInterface

Mostly for use in comparing results from previous versions of algorithms, and/or so we can know whether or not data in the database is based on an older version of the algorithm. Start with "return 1.0". Go up by whatever increments you like (e.g. 1.1, 1.2, etc. or 1, 2, 3, etc.)

Returns:

reinitializeMoreData

public void reinitializeMoreData()

Description copied from class: EfficientPebbleAlgorithm

If resetWithThesePebbles is called, what else needs to be reinitialized before the algorithm can be run? This is supposed to be much more efficient than calling initializeMoreData. The idea is that the graph didn't change, but the data did, so we only need to reinitialize some things.

Specified by:

reinitializeMoreData in class EfficientPebbleAlgorithm

parseArguments

public void parseArguments(java.lang.String args)

Description copied from interface: AlgorithmInterface

Sends a string that the user can enter to the algorithm. The string will be in whatever format the user enters. Implementation can assume this method is called after the problem data has been set. Throw an exception if different arguments are required.

argumentFormat

public java.lang.String argumentFormat()

Description copied from interface: AlgorithmInterface

Describe how the argument(s) to the algorithm should be formatted, if applicable.

Returns: