The LEOR Method is a 3x3 method which combines aspects of Roux and ZZ, although it seems to be described best as a variant of Petrus.
It was first conceived of by Arc and Pyjam1, although it has its precursors in the works of Joseph Briggs and Noah Arthurs2.
As stated earlier, EOStripe is the defining feature of LEOR, but due to its uniqueness, it is often also the biggest problem for those wanting to switch, especially as resources are very scarce.
Therefore, to aid the general understanding of EOStripe, this section compiles some information on it.
The following is a table of all EOStripe states sorted by their <R, r, M, U>-gen movecount in STM.3
Depth | New | Total | % of all |
---|---|---|---|
0 | 1 | 1 | 0,00136% |
1 | 3 | 4 | 0,00543% |
2 | 9 | 13 | 0,0122% |
3 | 63 | 76 | 0,0854% |
4 | 210 | 286 | 0,285% |
5 | 1110 | 1396 | 1,51% |
6 | 2968 | 4364 | 4,03% |
7 | 12069 | 16433 | 16,4% |
8 | 20026 | 36459 | 27,2% |
9 | 26641 | 63100 | 36,1% |
10 | 8730 | 71830 | 11,8% |
11 | 1814 | 73644 | 2,46% |
12 | 82 | 73726 | 0,111% |
13 | 2 | 73728 | 0,00271% |
14 | 0 | 73728 | 0,00% |
Average movecount: 8.37 STM
As LEOR only has a small userbase which, as of now, contains no one who is world-class, LEOR’s potential still remains unproven and as such, not much can be said about its viability, although it currently appears that it might be most effective for one-handed solving due to favoring 2-gen solving.
Furthermore, it may also be used as a 4x4 method for people coming from ZZ who prefer doing EO on big cubes without the problems that EO-first steps like EOLine and EOCross pose.
Because LEOR has much in common with other more popular methods, resources for all steps - with the notable exception of EOStripe - are generally readily found.
The following list is a hopefully comprehensive but still incomplete selection of them:
based on the members of the LEOR discord
https://www.speedsolving.com/threads/roux-breaker-the-yruru-method.77201/post-1367918 ↩
https://www.speedsolving.com/threads/noahs-cp-block-method-2-0.41986/ ↩
Movecounts from ksolve++ using custom eostripe.def ↩