OLL Numbers

Zarxrax

Veteran
Joined
Jan 7, 2009
Messages
1,282
Location
North Carolina
On the wiki here, and on other sites, OLLs are given a number. However, the numbers used for each case vary from site to site.
I'm wondering what listing out there would come closest to a generally accepted "official" numbering, if such a thing even exists?
 
I vote that we use a more descriptive notation like one letter for the basic shape and then a number. This way, OLL 46 (a number that probably zero people have memorized) would be named C1 or C2. This notation is reflected in the table at the top of the OLL wiki and completely spelled out on badmephisto's speedcubing PDF here: http://kungfoomanchu.com/guides/badmephisto's-speedcubing-method-v2.pdf (on the 3rd page).

I think this would be much easier for people to remember and then we will actually all be able to quickly use names for each OLL that everyone will know (instead of "good C" or "bad C").
 
I completely agree with Andy, it makes the most sense. I also think though that the common nicknames (such as Sune, Anti Sune, fat sune, etc) would be acceptable for those that make sense.

Andy you should check your PM box :P
 
Well...I don't know if you would really want to memo the numbers of all the OLLs.
On topic: I don't think there is an official number for every OLL.
 
I consider the speedsolving wiki to be the canonical numbering, since I believe it has stayed the same and has been the most referenced.

If you're considering introducing another system, I would just say: Good luck. Do it right and be careful.

Does the system used on the wiki actually follow any sort of logic? Out of every system I have seen, it seems the most random. OLLs that are in the same "family" can have wildly different numbers.
Heck, the wiki page itself isnt even sorted by the numbers it uses!
 
I consider the speedsolving wiki to be the canonical numbering, since I believe it has stayed the same and has been the most referenced.

If you're considering introducing another system, I would just say: Good luck. Do it right and be careful.
Agree. This is the center of the cubing universe, and if the wiki says that this is OLL 41, then by God, it's OLL 41.

If Jessica Fridrich had numbered them as she named the PLL's, then I would consider that the gospel, but she didn't, so.

Still, I prefer nicknames for everything, including F2L cases. I would like to see some more standard nicknames like "Sune" for all 57 OLL's...but I figure they will fill in with defacto standard labels as certain names stick over time. Give it a few years and a little help from some creative people.
 
I vote that we use a more descriptive notation like one letter for the basic shape and then a number. This way, OLL 46 (a number that probably zero people have memorized) would be named C1 or C2. This notation is reflected in the table at the top of the OLL wiki and completely spelled out on badmephisto's speedcubing PDF here: http://kungfoomanchu.com/guides/badmephisto's-speedcubing-method-v2.pdf (on the 3rd page).

I think this would be much easier for people to remember and then we will actually all be able to quickly use names for each OLL that everyone will know (instead of "good C" or "bad C").

This seemed like a good idea, but there is a big problem, and perhaps you have overlooked it as well.
There are two different sets of "L" cases!
 
Uhh why not just corners plus edges? Like OLL 3
O3.gif
becomes NEO Sune, theres only 4 types of edges and 8 possibilities for corners. the difficulty would be mirrors, but it's still possible. I would still call most of the easy ones by the names I hear most, like Easy P/6 Move T, 8 Move T, Easy C, Fat Sune etc.
 
OLL Table for beginners

Hi,

I'm working on an OLL table,
the idea is to create an OLL table for beginners ...
(with the aim to ease memorization)
and I'm introducing some new features (such as matrix notations for algs that should simplify memorization).

Anyway, regarding names, I made the following choice:

Serifs: I call serifs the lines used to represent stickers not on the U face.

Names: I give the OLLs names that describe not just the image in the U face but also the greatest number of adjacent serifs or the configuration of serifs.

Here's the table.

So for instance V2 represents case 48 'cause there's a V and a maximum of 2 adjacent serifs.
While V3 (or V Bar) represents case 53 'cause there's a V with a maximum of 3 adjacent serifs.
Finally V23 (or V2 Bar) represents case 49 'cause there's a V with 2 adjacent serifs on a side and 3 adjacent serifs on another side.

Not all serifs are shown in my OLL images, but just the ones needed to recognize the case.

I use primes (') in names to indicate symmetrical cases.

There are some details and improvements that still need to be completed in my table.

Hope my english is clear enough
and that this is somehow useful.
 
Last edited:
Zarx: By two sets of L do you mean L1-L4 (referred to as knight move shapes on the wiki) or do you mean knight move shapes being one group and then the F SM SM F' type L (small L, some people call it caret, etc)?
 
Zarx: By two sets of L do you mean L1-L4 (referred to as knight move shapes on the wiki) or do you mean knight move shapes being one group and then the F SM SM F' type L (small L, some people call it caret, etc)?

I mean the "L shapes" (L1-L6)
and then the Lightning bolts (L1-L4 & L5-L6)

Those are the labels used on the wiki.
I'm not talking about the knight move shapes at all.
I would propose naming the lighting bolt ones "LB" instead of just L.
 
I have my own names for the oll cases. It is like the poster with 'serifs' where I call the u face pattern by the name and then I add bar, double sune, etc for the pattern of the LL sticker. So, the case above in previous poster is 2 dot floating (like g-perm floating column). And then of course the name of the u faces I use are pretty much the same across the board; all the edges oriented ones, h oll, x oll, knight, kite, c, etc... I actually call c oll 'ear' oll, because it looks like an ear to me when on left or right... I like the families idea for oll becaus e when I referenced the wiki, I learned in families, leaving the families with the most cases for the end. I would like to see this on the wiki as well instead of numbers, as it is much easier to reference an algorithm from a family and then the specific case rather than sifting through a random directory of OLLs... I need to learn some batter algs for some cases and I specificially remeber being too lazy to sift through the randomness of the wiki and many others' oll pages to learn better algs.... I wish I had the time and patience to rearrange them, but I would for sure appreciate someone who dedicated themselves to give the olls some kind of sane organization!
 
guzman - that table is, in my opinion, horrible for beginners. Beginners can barely read off algs and perform them correctly as it is, let alone trying to decypher the notation first. Just write the algs as the are, and group together similar moves. Also, i think your pictures/naming and alg choice is poor.
 
guzman - that table is, in my opinion, horrible for beginners. Beginners can barely read off algs and perform them correctly as it is, let alone trying to decypher the notation first. Just write the algs as the are, and group together similar moves. Also, i think your pictures/naming and alg choice is poor.

Well, first of all, thanks, your comment helps me.
I actually first made the table for me
and this is how I learnt all the Oll's.
And the Oll's are the first thing I learnt.

My idea was that memorizing lots of algs may become difficult if the algs are just a bunch of random letters.
So I decided to look for patterns and I found out that almost all the oll's are just obtained but mixing
some very basic four letter commutators. This fact becomes very visible if you use a compact notation
for basic commutators (such as [r,u] or simply [ru]) and if you write algs in matrix form:
for instance, I find way more easy to memorize
R
U2
R' - [R'F]
U2 - [R'F]

with its structure that clearly shows the mixture of two commutators (namely [R U2] and [R'F]), than
RU2R2FRF'U2R'FRF'

But I understand that writing things in matrix form and with compact notations creates an obstacle.

For what concerns names I think that the name should describe not only the image of the yellow stikers on the U face,
but also, if possible, the position of the yellow stickers not in the U face.
I find more clear the names C1 and CBar than case 34 and case 46.

Finally, when I said beginners I didn't mean total beginners
but of course the algs are not optimized.

Anyway, I understand what you say and my table is just an experiment.
 
Last edited:
Back
Top