Week 23: Finished Algorithm to Get All Solutions

[rolivia]

@twood02 @cctoombs

Algorithm to generate all possible solutions

Finished the algorithm to generate all of the possible solutions to a puzzle. It works for small puzzles, but it crashes for puzzles bigger than 4x4, 5x3, etc.
(Based on the error message I think that it is too slow: "Warning: Unresoponsive Script. A script on this page may be busy, or it may have stopped responding. You can stop the script now, open the script in the debugger, or let the script continue. Script: http://localhost/LogiClass/testing/LCinterface.js:188"). For now, I am trying to get the main algorithm (to generate a list of clues) to work for small puzzles. Later, I will try to optimize the algorithm to get all of the possible solutions, but if that does not work, I may need to rethink my algorithm for generating a clue list.

All relevant code is located in testing/LCinterface.js.

Code:

• https://github.com/gwsd2015/LogiClass/blob/master/testing/LCinterface.js : Contains functions pertaining to the clue-generation algorithm and functions that serve as interfaces for the datastructures
• https://github.com/gwsd2015/LogiClass/blob/master/testing/datastructs.js : Contains data structures for the puzzle and functions for using them
• https://github.com/gwsd2015/LogiClass/blob/master/testing/clues.js : Contains all clue algorithms I have written so far.
• https://github.com/gwsd2015/LogiClass/blob/master/testing/error.js : I use this to systematically log error messages.
• https://github.com/gwsd2015/LogiClass/blob/master/testing/main.js : Test file
• https://github.com/gwsd2015/LogiClass/blob/master/testing/print.js : I use this to print some of the data structures for testing purposes
• https://github.com/gwsd2015/LogiClass/blob/master/testing/testing.html : Used for testing
• https://github.com/gwsd2015/LogiClass/blob/master/testing/unitTests.html : Used for testing
• https://github.com/gwsd2015/LogiClass/blob/master/testing/unitTests.js : Used for testing

[twood02]

sounds good. Keep your final demo in mind and be sure that what you are building will lead towards that goal.

Is your clue algorithm just run once when a puzzle is first created by the itnsructor, or will it be run every time a student loads the page? That will affect how much effort it is worth putting in to optimize it.