Misrecognition between Roux/CFOP

[hakatashi]

Examples Follows:

• https://alg.cubing.net/?setup=F2_D_F2_D-_F2_D_B2_U_B2_U2_R2_D-_B_D-_R_D2_B2_R-_B2_F-_R&alg=F_U-_L_B2_%2F%2F_%221st_block%22%0AU2_B-_U_F-_D2_F_D-_R-_D_R2_D_R-_D_R_D_R-_L_D2_L-_D_L_D-_L-_D-_L-_D_L_D_L-_D_L_D-_L-_D-_L_D_F_D_L_D-_L-_F-_D-_R_D2-_R-_D-_R_D-_R-_D-_R-_D-_R_D_U-_R2_D_R-_D_R_D-_R_D-_R2-_U_D_%2F%2F_%222nd_block%22
• 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]

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]

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]

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

[hakatashi]

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.