Nautilus: A versatile 3x3 method

And how is that?
@trangium 's ELLs, which are the best out there that I know of average 10.27 moves. inserting the DF edge is around 3 moves + AUF, so around 3.75. 3.75+10.27= 14.02 moves.
Now. EO averages around 5 moves. L5EP averages 7.38 moves according to the Nautilus L5E algsheet. 7.38+5=12.38 however we need to include AUF so add 1.5 moves (two AUFs), that makes 13.88.
EO+L5EP is more efficient than DFM+ELL.
 
Now. EO averages around 5 moves. L5EP averages 7.38 moves according to the Nautilus L5E algsheet. 7.38+5=12.38 however we need to include AUF so add 1.5 moves (two AUFs), that makes 13.88.
L5EO has 5 cases with 7, 7, 7, 7, 3 moves (excluding AUF). Wouldn't that be 6.06? Or are the EO algs on the Nautilus website not good movecount wise?
6.06+7.3 = 13.44 + AUF[=.75 x 2] = 14.98
(technically 13.45 since 6.06=6.0625)

Am I just being stupid?

Edit: Where do I find trangiums ELL's?
Edit Edit: nvm they're on his Github.
 
Last edited:
L5EO has 5 cases with 7, 7, 7, 7, 3 moves (excluding AUF). Wouldn't that be 6.06? Or are the EO algs on the Nautilus website not good movecount wise?
6.06+7.3 = 13.44 + AUF[=.75 x 2] = 14.98
(technically 13.45 since 6.06=6.0625)

Am I just being stupid?

Edit: Where do I find trangiums ELL's?
Edit Edit: nvm they're on his Github.
Ok. I miscounted. So DFM+ELL is slightly more efficient. HOWEVER. That does not mean that DFM+ELL is as fast as EO+L5EP. EO has amazing recog. DFM has great recog. Now ELL recog is kind of eh. L5EP recog is very good. EO+L5EP is faster, as it sacrifices one move for way better recog.
 
And how is that?

By my estimation, rounding up to imprecisely account for AUF:

L5EOP: 7.5 moves (20 cases)
EPLL: 7 moves (4 cases)
= 14.5 moves (24 cases)

L5EO: 6.5 moves (5 cases)
L5EP: 8 moves (16 cases)
= 14.5 moves (21 cases)

place DF: 3.5 to 4 moves (intuitive)
ELL: 11 moves (29 cases)
= 14.5 to 15 moves (29 cases)

The ELL approach might be comparable if you omit the case where the DFM edge is flipped in DFM.

They definitely all seem to be pretty close.
 
Bump. Can someone help me understand the L5E description?

I refer to this site:

Namely this part in the excel table:
1. Locate the DF edge.
2. Locate the L/R edges. If the DF edge is on the U layer, the L/R edges will be the two that belong in the corner slots to the left and right of the DF edge. So these two edges won't always be the UL+UR edges, but can also be the UF+UB edges. If the DF edge is permuted, then you kind of have an ELL case but with more possible edge orientations. Recognition can be similar to EPLL. If there is a permuted edge, the UL and UR colors will be those to the left and right of that edge. If there isn't a permuted edge, then it is one of the other two EPLL cases.
3. Determine the edge orientation and execute the algorithm.

Steps 1 and 2 can likely be seen before and during performance of the CLL algorithm.

1. What does it mean "corner slot", when we only have unsolved edges at this point?
2. What does it mean "if DF edge is permuted"? A single element cannot be permuted. Does it mean "not in its place"? Does it mean "in its place but misoriented"?
3. It says nothing about the tabs of the excel table: what is L/R Adjacent, L/R Opposite, and L/R 1U1D?
 
Bump. Can someone help me understand the L5E description?

I refer to this site:

Namely this part in the excel table:


1. What does it mean "corner slot", when we only have unsolved edges at this point?
2. What does it mean "if DF edge is permuted"? A single element cannot be permuted. Does it mean "not in its place"? Does it mean "in its place but misoriented"?
3. It says nothing about the tabs of the excel table: what is L/R Adjacent, L/R Opposite, and L/R 1U1D?
If the DF edge is on the U layer, you find the two edges that belong in the two slots to the left and right of it (the slots between the corners). For DF edge being permuted it means in its correct position but either oriented or misoriented. The tabs refer to the locations of the two left and right edges that belong to the left and right of the DF edge if it's on the U layer. The two edges can be adjacent to each other, opposite to each other, or one can be on the U layer and one can be on the D layer.

I designed this recognition method for versatility, so that it can also be used in pseudo situations. I think many would prefer a recognition method based on checking EO then EP. But someone else would have to create a new sheet that reorganizes the cases.
 
If the DF edge is on the U layer, you find the two edges that belong in the two slots to the left and right of it (the slots between the corners). For DF edge being permuted it means in its correct position but either oriented or misoriented. The tabs refer to the locations of the two left and right edges that belong to the left and right of the DF edge if it's on the U layer. The two edges can be adjacent to each other, opposite to each other, or one can be on the U layer and one can be on the D layer.

I designed this recognition method for versatility, so that it can also be used in pseudo situations. I think many would prefer a recognition method based on checking EO then EP. But someone else would have to create a new sheet that reorganizes the cases.

So, if the DF edge is on the U layer, let's say on the UL place; it means that the "L/R edges" are the UB and UF edges, right?
Do you adjust the top layer in this case? Do you have to do a U' move so the DF edge (sitting in UL originally) moves to UF, and the "L/R edges" actually move to L and R places?

EDIT:
For example, this case:
 Twizzle link 
 Setup 
x2 U M' U' M U2 M' U M U
 Moves 


I have to do a U' move, and now it matches this case on the table (L/R adjacent):
1782719428571.webp

Because DF edge is the white-blue sitting on top left, and after a U' move, L/R edges are the yellow-blue and yellow-green; they are adjacent on the top layer, on UL and UB, and UL sitting at UB.

And the overall solution is:
 Twizzle link 
 Setup 
x2 U M' U' M U2 M' U M U
 Moves 
(U') M' U' M U2 M' U M (U')
 
Last edited:
So, if the DF edge is on the U layer, let's say on the UL place; it means that the "L/R edges" are the UB and UF edges, right?
Do you adjust the top layer in this case? Do you have to do a U' move so the DF edge (sitting in UL originally) moves to UF, and the "L/R edges" actually move to L and R places?

EDIT:
For example, this case:
 Twizzle link 
 Setup 
x2 U M' U' M U2 M' U M U
 Moves 


I have to do a U' move, and now it matches this case on the table (L/R adjacent):
View attachment 49744
Because DF edge is the white-blue sitting on top left, and after a U' move, L/R edges are the yellow-blue and yellow-green; they are adjacent on the top layer, on UL and UB, and UL sitting at UB.

And the overall solution is:
 Twizzle link 
 Setup 
x2 U M' U' M U2 M' U M U
 Moves 
(U') M' U' M U2 M' U M (U')
Looks like you got it. For your question about AUF, you don’t necessarily have to AUF unless it personally helps you to for recognition or if its the correct AUF before executing the alg. With practice the full L5E case can probably be predicted while solving the corners, making it even less necessary to AUF to help recognize a case.
 
Looks like you got it. For your question about AUF, you don’t necessarily have to AUF unless it personally helps you to for recognition or if its the correct AUF before executing the alg. With practice the full L5E case can probably be predicted while solving the corners, making it even less necessary to AUF to help recognize a case.
To be honest, not gonna learn it (I have trouble learning new algs and methods anyway); but I have to admit, it's fun to play around with it, and of course I highly appreciate all the efforts you put into this method. It's a fun method, and I see its potential.
But I think I'm gonna add more to the example solves; especially since I use what I noticed an unusual color scheme for first block (red/orange bottom, white/yellow left).

Thank you for the help and clarification!
 
I’ve decided to switch over to this method. CFOP grew stale for me and I’ve always wanted to try something new. My CFOP avg is 14 secs. I think I will understand cubing more using this method and also have more fun. Wish me luck!
 
Back
Top