Interesting...it is lighting fast at producing a solution but the solutions are huuuuge. For a scambled 5x5x5 is produced a solution 1067 steps long!
230 steps to solve the centers
675 steps to pair the edges
162 steps to solve the 3x3x3
That is the only web-based solver that I know of for...
This will print the cube and the kociemba string for a scrambled 17x17x17
from rubikscubennnsolver import configure_logging, RubiksCube
from rubikscubennnsolver.RubiksCubeNNNOdd import solved_171717
configure_logging()
cube = RubiksCube(solved_171717, 'URFDLB')
cube.randomize(count=2000)...
My apologies for replying a year and a half later :( I tried those two cubes and they are both working today on later master. Can you try
git pull
make clean
make init
source ./venv/bin/activate
and try to solve those cubes again.
It is because of the f-strings, this feature was introduced in python3.6 but you are running 3.5. I should have the installer catch this and raise a better error.
In a nutshell though if you upgrade to python 3.6 or later you should be good.
I write code for a living and as a hobby :) I do a lot of lego mindstorms projects for fun and one of those was a rubiks cube solving robot which led me down this path of writing a NxNxN rubiks cube solver.
I just pushed a fix, the odds of hitting that bug were 1 in 40,320!! :) There is one more bug to fix here, for some reason the entire cube rotations (x, y, z moves) are not being removed as they should be.
It takes about 4s per move so for say a 5x5x5 if you want to do 70 moves to scramble you are looking at about 5 minutes.
I have never been to a cube solving competition...how many cubes do volunteers end up scrambling? I take it they are given a set of moves to apply to scramble a cube a...
I built this, it can solve 2x2x2 up to 6x6x6:
https://rebrickable.com/mocs/MOC-12712/dwalton76/cranecuber/
It would be an easy change to feed it a sequence of steps to apply to a solved cube to scramble it a specific way.
FYI I have installed my solver on a pi3 and will use that for testing in the future. 4x4x4 takes ~10s, 5x5x5 takes ~180s, 6x6x6 and larger run out of RAM and do not produce a solution. Am going to work on making this run faster on pi3 but the solutions will be a little longer than "--normal" mode.