Random Blindfold Cubing Discussion

I was looking for the best alg for Ubr-Bdr-Rbd
Ok I added cube rotations to generator and also a sorter based on a primitive efficiency estimator. It's a bit better now.
R' [r, d' R2 d]
R2 [r, d' R' d]
r' [r', u' R' u]
R U' [d, r' U r]
U' R [d, r' U r]
U' Rw' [U, r' u r]
Rw' U' [u, r U r']
R2 u [r', U' l' U]
r2 [r, u' R' u]
[r', D' b D]
[b, D r' D']
x' U' [u, r U r']
Rw D' [d, r D r']
R y' [d', r' U r]
R U2 [d, r' U2 r]
U2 R [d, r' U2 r]
r' d [r, U' l U]
U' r' [U', l' d l]
R y [d', l' U l]
U2 Rw' [U2, r' u r]
Rw' U2 [u, r U2 r']
R' z' [u, r' U2 r]
z' U' [u, r' U2 r]
R2 z' [u, r' U' r]
z' U2 [u, r' U' r]
x D' [d, r D r']
U2 Rw' [U2, l' u' l]
x' U2 [u, r U2 r']
Rw D2 [d, r D2 r']
R2 z [d, l' D' l]
r' z [d', r' D' r]
r' z' [u', l' U' l]
R' z [d, l' D2 l]
r' Uw y [l, U' r U]
r' Uw y' [r, U' l U]
r' y Uw [l, U' r U]
r' y' Uw [r, U' l U]
r2 d [r', D' l' D]
z D' [d, l' D2 l]
z D2 [d, l' D' l]
R x' [r', u' R' u]
x' R [r', u' R' u]
x D2 [d, r D2 r']
R x [r', d' R' d]
x R [r', d' R' d]
r2 z [d, r' D' r]
r2 z' [u, l' U' l]
R r' [r', u' R2 u]
r' R [r', u' R2 u]
R' U' R2 [d, r' U r]
R2 U' R' [d, r' U r]
U R U [d, r' U2 r]
U R U2 [d, r' U r]
U' R U' [d, r' U2 r]
U2 R U [d, r' U r]
r' Uw' [R, d l' d']
R2 U' u [l', U r' U']
R2 u U' [l', U r' U']
U' R2 u [l', U r' U']
d L' [d', l U' l']
y R [r', d R2 d']
y R2 [r', d R d']
R' r [r', d' R2 d]
R2 r [r', d' R' d]
r R' [r', d' R2 d]
r R2 [r', d' R' d]
Rw2 [f, U r' U']
Rw2 [r', U' f U]
B' [d, l U' l']
R' U' r' [U, r' u r]
U' R' r' [U, r' u r]
U' r' R' [U, r' u r]
y r [r, u R u']
R' r' U' [u, r U r']
r' R' U' [u, r U r']
r' U' R' [u, r U r']
d Lw [U', l u' l']
R U' r' [U, r d r']
U y R' [d', r U' r']
U' R r' [U, r d r']
U' r' R [U, r d r']
U' r' U [U, r' d' r]
y R' U [d', r U' r']
y U R' [d', r U' r']
r' Uw2 [l', u R' u']
R2 x' [r', u' R2 u]
x' R2 [r', u' R2 u]
R d' [d', l' U2 l]
y Rw U [u', r' U' r]
R x' d [r, U' l U]
x' R d [r, U' l U]
U y Rw [U', r u' r']
r' U' d [l, U r U']
r' d U' [l, U r U']
y U Rw [U', r u' r']
Rw' u' [u', l U2 l']
R2 x [r', d' R2 d]
x R2 [r', d' R2 d]
d l [U, r d' r']
R' U' x' [u, l' U' l]
U' R' x' [u, l' U' l]
U' x' R' [u, l' U' l]
z' u' [u', l' U' l]
..... (970k results there)
b2 z y f2 b2 [u', b D' b']
 
I recall seeing a nice alg for wing parity in big-BLD, for r2, somewhere in these forums not too long ago. But literally an hour of trying to get the forum search tool to do what I want, and manually searching through many of these threads, I can't find it. Anyone know where it was?
 
After many different approaches, I may have found the ideal way for me to drill my 3Style comms on a more productive way.

I'll be using Anki. This is an amazing flashcard app for anyone to learn anything through spaced repetition. I have successfully used it in the past to expand my German vocabulary and more recently to learn the Major Mnemonic System.

I have created a deck where I'll be adding new comms as they are discovered, and using it to drill them randomly.

Each flashcard has a letter pair as the front, which is prompted to me and then I'll perform the case on a solved cube. If I succeed, and depending on how fluent / fast at recalling and executing it, I'll repeat a few times over before moving on to the next one. Tapping the flashcard will show the respective algorithm in case I need to double-check it.

What's amazing to me about Anki is that it makes me focus on a specific case, one at a time, and their appearances will be prompted depending on how much I need to practice each, which is to say my worst cases will show up more often so I drill them more intensively. The better I get at a case, the less it shows up until it needs refreshing.

My previous approach was kinda random, and I found I was not focusing properly. I'd drill random cases from my spreadsheet and not make much progress, with a few real time solves in between - in which I'd often forget or downright panic when I came across a case I had a comm for, resorting to OP. It was still feeling kind of overwhelming, and clearly counterproductive.

Now my first Anki session led me to about 45min of focused practice on just the comms I have and need to get good at, and I'm far more confident in most of the cases already.

Tomorrow I'll start working on an upgraded practice regimen. I'll warm up with an Anki session of 20 random comms, do a couple Ao12s and then back to Anki, followed by trying to come up with new comms for the cases I still need to learn.

Rinse, repeat, and hopefully have the FDR sticker set fully implemented within a week or so, depending on how much practice time I get.
Thanks for sharing the tip! I've also started using corner 3-cycles, that wasn't as difficult as seemed in the beginning. I guess I might start using a flashcard app too as I get to a bit more complicated comms.
 
I recall seeing a nice alg for wing parity in big-BLD, for r2, somewhere in these forums not too long ago. But literally an hour of trying to get the forum search tool to do what I want, and manually searching through many of these threads, I can't find it. Anyone know where it was?
Was it this one?

r' U2 r U2 r' U2 x r U2 r U2 r U2 r2 U2 x' r' U2

Rob Yau posted it a few years ago in one of the megathreads but search isn't so good at finding things buried in those :)
 
After many different approaches, I may have found the ideal way for me to drill my 3Style comms on a more productive way.

I'll be using Anki. This is an amazing flashcard app for anyone to learn anything through spaced repetition. I have successfully used it in the past to expand my German vocabulary and more recently to learn the Major Mnemonic System.
Last year I made a Windows app for drilling 3-cycles. Don't think I ever mentioned it here on the BLD forums, so better late than never. :) You can check it out here:

https://www.speedsolving.com/forum/threads/bldtrainer-new-application-for-practicing-3-cycles.61303/

It can be used in a variety of ways, for example to focus on 3-cycles involving a specific sticker.
 
This is AMAZING! Thanks for sharing!
Thanks, I'm glad you like it! :)

Originally I planned to make a small simple tool to practice with myself, but then I got more interested in adding features to the app than actual bld practice. And by the time I was done with the app my cubing interests had moved on to other events, so I never really got around to use the app myself much. One day I'll get back to working on bld, then I'll use it for sure!
 
After using M2/OP for ages, I switched to corner comms. I use UBR and DF. I don't have any intention of switching to edges comms any time soon, but it might happen later on, who knows. What I'm more interested in right now is switching to centers comms (x and +).

Since I use UBR for corners, should I use Ubr for x-centers? Will it make coming up with comms easier? Does it matter much? Most people seem to use the same piece for corners and x-centers. I currently use Ufl but don't mind switching. The comms I use for UBR are all <R,U,D,L> with no rotations. I intend to come up with rotation-less comms for other pieces too.

I'm more interested in what I'm going to do for +-centers. Would it be best to stick with Df because I use DF for edges (and then if I switch to edge comms down the road they will be similar), or should I go with something on U? I currently use Df with M2 execution (just like for edges).

I understand that personal preference is a big factor, and many different buffers can be equally good. I just want to see what people think before sitting down and starting to play around with center comms. If this has already been discussed elsewhere in the forum, please link it. I didn't really find what I was looking for with a brief search.
 
I use UBL for corners and also for X centers. I do find it makes it easier to see some commutators I might not otherwise see. I also use UB for + centers; I find that the comms for UBL X centers and for UB + centers are very similar, so I find it helpful. And I use UBL and UBR for obliques too on bigger cubes, for the same reason - all the comms are somewhat analagous (except that some + centers and especially obliques are easier because they have more options because things aren't as in the way).
 
Dunno if this is already a thing or not, maybe someone can tell me. I was having another think about finally working on useful edge 5-cycles to deal with some awkward cases, and realised there's a different trick which is much simpler and works for other piece types too. Here's an example with DF buffer.

Targets: FU UB UL RU
Cycles: DF>FU>UB, DF>UL>UR

Now, DF>FU>UB isn't the nicest case, but it can be avoided by considering the whole situation as a 5-cycle and splitting it up into 3-cycles differently, by noting that FU>UB>(not M slice) cases are nice.

Alternative solution: FU>UB>UL, FU>RU>DF (= FU>UB>UL, DF>FU>RU)
 
I wrote a quick BLD analyzer earlier and ran it on a few thousand scrambles and thought the results were interesting so I figured I'd post them.

CountCorner TargetsEdge TargetsSolved CornersTwisted CornersSolved EdgesFlipped Edges
00.0%0.0%75.0%57.0%61.8%63.5%
10.0%0.0%21.5%32.4%30.7%29.1%
20.2%0.0%3.1%8.4%6.8%6.5%
30.5%0.0%0.3%1.9%0.6%0.8%
42.8%0.0%0.1%0.1%0.1%0.1%
57.5%0.0%0.0%0.2%0.0%0.0%
620.6%0.0%0.0%0.0%0.0%0.0%
733.4%0.4%0.0%0.0%0.0%0.0%
824.9%1.8%0.0%0.0%0.0%0.0%
99.1%6.8%0.0%0.0%0.0%0.0%
100.9%16.8%0.0%0.0%0.0%0.0%
110.0%29.3%0.0%0.0%0.0%0.0%
120.0%28.1%0.0%0.0%0.0%0.0%
130.0%13.8%0.0%0.0%0.0%0.0%
140.0%2.8%0.0%0.0%0.0%0.0%
150.0%0.3%0.0%0.0%0.0%0.0%
Avg.6.98811.2810.2890.5620.4650.449

Screen Shot 2017-08-09 at 7.48.11 PM.png Screen Shot 2017-08-09 at 7.48.19 PM.png Screen Shot 2017-08-09 at 7.48.26 PM.png
 
I've got a question for people who use 3-style.

When you're recalling information from your images and executing it, do you first turn the images back into letters, then the letters into the right commutator? Or do you go directly from the image to the right commutator?

As an example, let's say you have a CaT in your memo.

Do you turn the image of a cat back into CT, then remember the commutator that you correspond with CT? Or do you directly correspond the image of a cat with the commutator?

Thanks!
 
I've got a question for people who use 3-style.

When you're recalling information from your images and executing it, do you first turn the images back into letters, then the letters into the right commutator? Or do you go directly from the image to the right commutator?

As an example, let's say you have a CaT in your memo.

Do you turn the image of a cat back into CT, then remember the commutator that you correspond with CT? Or do you directly correspond the image of a cat with the commutator?

Thanks!
I go directly from image to commutator. In fact, when I'm coming up with comms, I find it easier to think of it in terms of "the comm for cat" rather than the "the comm for CT".

Although It's the word cat, not the image of a cat that I associate the comm with.
 
Back
Top