Misrecognition between Roux/CFOP

hakatashi / smart-cube-timer

Proof-of-concept smart timer for GiiKER

https://hakatashi.github.io/smart-cube-timer/

MIT License

72 stars 22 forks source link

Misrecognition between Roux/CFOP #2

Open hakatashi opened 6 years ago

hakatashi commented 6 years ago

Examples Follows:

tussosedan commented 6 years ago

Ha, that's an interesting one! I suppose it can happen the other way around too, when while building FB a cross is created somewhere on the cube by chance. I'm not really sure how to solve this -- maybe by recognizing the next step in the solve?

tussosedan commented 6 years ago

This actually happened to me yesterday, here's the reconstruction

https://alg.cubing.net/?alg=z_L_U2_R2_L2-_F2_%2F%2F_Cross%0AD2_R_D_U_B2-_U-_D_U-_L_D_F2-_U_F_U-_D_R_U-_R2_R-_U_R_U-_R-_U-_B_U_B-_R2_U_D-_F_D-_U_L-_D_U2-_D_R-_D_U-_B2_D_U-_L2_%2F%2F_F2L_%232&setup=D-_B-_L_B_D_L_U-_B2_U_B_R2_F2_R2_F-_R2_U2_B_D2_F2

tussosedan commented 6 years ago

Or, to keep it simple, just have a configuration to select a specific method instead of auto-recognition.

hakatashi commented 6 years ago

Fmm... I still not prefer configuration, but I conceived the idea that, after few solves are detected as cfop (or roux) in a row, the timer “locks” detection and forces cfop (or roux) mode for future solves.