Are there any tips on how to look for pieces that you haven't memo-ed in 4bld?

A lot of times I find myself finishing memo quite fast but it felt like too little letters so I will go through the cube looking for solved pieces or short edge cycles I didn't notice, and that could take up to 1 minute, which is kinda frustrating at times. I will often be repeating my memo to myself to see if a piece is already in my memo.
 
Are there any tips on how to look for pieces that you haven't memo-ed in 4bld?

A lot of times I find myself finishing memo quite fast but it felt like too little letters so I will go through the cube looking for solved pieces or short edge cycles I didn't notice, and that could take up to 1 minute, which is kinda frustrating at times. I will often be repeating my memo to myself to see if a piece is already in my memo.

You sometimes will have an intuitive feeling that the upper-left-back of the cube was not cycled to very often, or the lower-front-right, etc. This doesn't happen often though, sometimes you really have no clue where the missing pieces could be located. The worst cases are when your cycles are (22)(2) or (21)(3). After memorizing a 22 cycle You often "feel" like you're done, when in fact you may still have a 2 cycle left. As for knowing when you're not done, have in mind what your ideal memo is like.

For me my ideal memo for wings is the following:
(PAIR PAIR PAIR) (PAIR PAIR PAIR) (PAIR PAIR PAIR) (PAIR PAIR SINGLE)

I don't memorize my buffer, since I always start at the same place, so a pure 24 cycle would be 4 locations, all pairs, except the last image is a SINGLE letter image.

If I memorized a 22 cycle it would be:
(PAIR PAIR PAIR) (PAIR PAIR PAIR) (PAIR PAIR PAIR) (PAIR SINGLE ______)

And I would notice the empty space, telling me I'm not yet done.

-------------------

Ok now to your question of how exactly do you find those pieces. Always search for solved pieces first, and account for them. If you're stuck with 2 or 3 remaining pieces then often I visually trace cycles to try to find them. I will look around to a part of the cube where I have some kind of intuitive feeling that I didn't cycle to that area as often as I maybe should have. I then pick a piece and visually follow the cycles as quickly as I can. If the cycles I am following start to feel familiar, or if I notice a letter pair that is an image from my memo and that fact stands out to me, then I abandon this cycle and pick another piece in that same area as before.

Finding 2-cycles is a lot easier. I just start from the A location, and see where that piece needs to go. If the piece where it needs to go is supposed to go back to A then I found my 2-cycle. If not, then I move to B and do the same thing. Finding a last remaining 3-cycle is the hardest for me. I just do that visual tracing method above.
 
Is there a decent alternative for the algorithm F [E, R U R'] F' M2 (It's used to shoot from DF to FR in M2).

I like the one to shoot to BD: M2 D R' [U R' U', M'] R D'

But the FR one is clumsy for me. Is there one in the BD style that anyone knows about?

Also, I have another question: Is this the proper way to write setup moves in commutator notation?: [Setup : A, B]
 
The inverse of the BD alg solves FR.
D R' [M', UR'U'] R D' M2
or you van use
D [M', UR2U'] D' R2 (and its inverse for BD)

And I belileve the correct notation is [S: [A, B]]
 
Last edited:
The inverse of the BD alg solves FR.
D R' [M', UR'U'] R D' M2
or you van use
D [M', UR2U'] D' R2 (and its inverse for BD)

And I belileve the correct notation is [S: [A, B]]

I think you meant D M' U R2 U' M U R2 U' D' M2 for the second alg, which I think is the best.

And the colon that denotes a conjugate has precedence over the comma for commutators, so [A : B,C] is correct without a second set of brackets. There is no rule set in stone, but I think the notation shown here is nice:

http://www.speedsolving.com/wiki/index.php/Commutator
 
I have seen it in use without nested brackets, but no one will get mad for using less ambiguous notation, that's for sure.

You had an R2 at the end instead of an M2. A pretty obvious mistake, but I thought I'd fix it. :p
 
Back
Top