You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When using your solver from the command line, it prints...
the scrambled 5x5 state
the reduction moves
the reduced three by three state.
At least I think it's supposed to be the reduced 3x3 state based on the fact that all centers and wings are always paired. However, there seems to be a bug with printing because after executing the reduction moves, my real 5x5 does not match the reduced 3x3 state printed out by your program. Most notably, the reduced 5x5 that gets printed "always" (sample of N=20 random states) has all corners solved.
It seems to affect the printing only. The internal String representation itself is fine, because passing that internal state to min2phase produces a correct solution that will indeed solve the physical 5x5 I'm using to verify the solution.
Is this an actual issue or is the second 5x5 printout supposed to be something other than the reduced 3x3 state?
The text was updated successfully, but these errors were encountered:
When using your solver from the command line, it prints...
At least I think it's supposed to be the reduced 3x3 state based on the fact that all centers and wings are always paired. However, there seems to be a bug with printing because after executing the reduction moves, my real 5x5 does not match the reduced 3x3 state printed out by your program. Most notably, the reduced 5x5 that gets printed "always" (sample of N=20 random states) has all corners solved.
It seems to affect the printing only. The internal
String
representation itself is fine, because passing that internal state tomin2phase
produces a correct solution that will indeed solve the physical 5x5 I'm using to verify the solution.Is this an actual issue or is the second 5x5 printout supposed to be something other than the reduced 3x3 state?
The text was updated successfully, but these errors were encountered: