Hi Everyone,

I wanted to let everyone know that my solve was fake.  I did not solve 
the Rubik's Cube blindfolded in 1:13.37 seconds.  (Though, when I hit 
the timer, I did indeed read 1:13.37.  Funny isn't it?)  I saw the 
solve and decided to practice a few times just to see what type of 
execution I could do.  You'll see that with a 23 second memorization 
time (which of course was fake...) the execution time was 50 seconds, 
which actually is quite doable.  Anyway, this fake solve brought up a 
few interesting points.

I think 23 second memorization is near impossible.  You'll notice my 
tapping of the cube.  Did I actually look at each piece when i tapped 
it?  The tapping, as one may assume, is me going through each piece in 
the cycle.  Well, to go from one piece to the next in the cycle, you 
have to look at one position, process the piece, and then look to the 
next position.  You'll see that I don't really turn the cube so I'm not 
really "looking" at the next position because I memorized it 
previously, I already knew where it was.  This is, of course, unless my 
tapping was fake as well, but that would have been such a nasty 
distraction.

So I guess I'm very interested in what type of memory techniques are 
used to memorize the cube in under 25 seconds.  Even if I could look 
around the three-dimensional cube that fast, how can one process 
information in the mind so quickly?  If you could process information 
in a one-pass memorization format at 1 second per piece of information, 
memorization of the cube could take place in about 30 seconds every 
time.  That, my friend, would be absolutely beautiful.

Also, solving with absolutely no delays is very difficult at that 
speed.  If I'm moving a cube that fast, I'm focusing on the physical 
moving of the cubes.  If I slow down a little bit, which might increase 
the overall physical execution time of the cube by as little as five 
seconds, the execution would be mindless enough for me to think ahead.

Anyway, I have some interesting question regarding the way Marcus did 
the solve because 1:22 is 7 seconds faster than my fastest real solve.  
Again, sorry for lying to everyone.

The algorithm R U2 R2 F2 R' U2 F2 R U' R2 U' R2 U' F2 D R2 D' you used 
to orient four corners... where did you find that?  Did you find that 
in A-cube or something?  I'm wondering why you use this algorithm.  Is 
it because of hand pain or some reason?  Because for five moves more, 
you could execute that using a two generator (only R and U) and 
furthermore, the 22-move algorithm for the four corner twist way easier 
to execute than that 17 move pain in the butt you're using.  Try a 
"Double Sune (TM by Lars Petrus Grand Copywriter of All Cubing)" + a 
U-permutation.  An example of this algorithm is:  (R U R' U R U' R' U R 
U2 R')(R2 U' R' U' R U R U R U' R).  I know the R' connected to the R2 
is redundant, but it illustrates the connectedness of the two 
algorithms and the speed at which it could be done with.  I would 
definitely suggest using this algorithm as opposed to the 17-move 
algorithm you have there.  I could easily shave off a few seconds.

Just to let you know, F D2 (L' B' L U')x5 D2 F solves all six-edges 
much more quickly.

Your general solve technique is very similar to what I used to do.  
When I started BLD cubing in New Mexico, especially with the 
orientations, I favored simplicity over efficiency.  Unfortunately, the 
sheer number of moves with me moving at maximum hand speed still 
produced execution times of around 70 seconds.  I'm much better now 
that I'm able to find more artful solutions to corner orientations and 
edge orientations (see hex-flip).  For the corner orientation in this 
case, I did y' [(U2 R U2 R')(U R U' R')]x2 y and then solved the 
remaining three (which is probably faster unless your pair-corner 
orientation of Sunes is absolutely insane).

Anyway, you said you memorized this one relatively fast but didn't give 
an actual time.  I typically don't know the times of my memorization if 
I don't look up at the clock.  Anyway, if you had 15 second 
memorization, that would leave under 70 seconds for the solve.  Your 
execution must be at the same hand speed as mine to accomplish this, 
and you must be lacking delays in totality.  How do you cube through 
this hand pain?

Also, is the reason that you remember these obscure BLD algorithms, 
such as odd 4-twists and corner diagonal permutations, but not OLL and 
PLL because you practice BLD more?  Why are you using algorithms such 
as (R2 U F2 U' F2 U' R2 U F2 U F2 U') in favor of more rudimentary 
algorithms such as (R' F R F')x3, especially if algorithm retention is 
difficult for you?

By the way, my actual time for this solve was a big fat fail.

Tyson Mao
Astrophysics '06
California Institute of Technology

On Feb 26, 2006, at 9:41 PM, kyuubree wrote:

> (look at L face) R U2 R2 F2 R' U2 F2 R U' R2 U' R2 U' F2 D R2 D'
> (look at F face, then D face) U2 R' U' R U' R' U2 R U2 R U R' U R U2
> R'
> (turn quarter turn clockwise) U2 R' U' R U' R' U2 R U2 R U R' U R U2
> R' (back to F face)
>
> D2 R2 (corner cycle UBL UFL UFR) R2 D2
> D' (R2 U F2 U' F2 U' R2 U F2 U F2 U') D
> B2 (corner cycle UFL UFR UBR)
> (U F2 U' F2 U' R2 U F2 U F2 U' R2) B2
>
> F' (R2 D' R2 M2 4(M'U) R2 M2 D R2) F
> F2 (turn quarter turn clockwise) (M' U M' U M' U2 M U M U M U2) F2
> (back to F face)
>
> U B' F' (edge cycle forwards) F B U'
> F2 B2 (edge cycle backwards) B2 F2
> D B2 (edge cycle forwards) B2 D'
> D F2 (PLL alg, dual adjacent-edge swap) F2 D'
>
>
> 1:22
>
> Memorization was very easy on this one but there were a lot of
> steps; the corner orientations were such that all U/D colors were on
> the L face, and there were two pairs of corresponding 2-1-corner
> twist orientations across the U and D faces on the R face.  The
> corners took me the longest but in general there wasn't anything
> gross.  The edges were very agreeable and didn't have any real
> issues at all -- no pausing needed, especially the last step which
> usually requires a bit of finaggling to get it to work (since the
> edge permutation cycles were in two large cycles, usually I simplify
> until the end and then figure out how to arrange them, but in this
> case it was a quick setup to a PLL alg).
>
>
>
> --- In [email protected], Tyson Mao <[EMAIL PROTECTED]>
> wrote:
>>
>> D2 F2 U' F' D2 B' U' L F' D2 L F' L2 B2 F D' F' U2 D2 B D2 L B2 U2
> D'
>>
>> I scramble white on top, green in front, and solve the same way.
>>
>> Tyson Mao
>> Astrophysics '06
>> California Institute of Technology
>>
>> On Feb 26, 2006, at 2:01 PM, Pedro wrote:
>>
>>> Tyson...the crowd is asking for the scramble! Please...(at least
> one
>>> person...hahahaha)
>>>
>>>   Pedro
>>>
>>> Tyson Mao <[EMAIL PROTECTED]> escreveu:
>>>   1 minute 13.37 seconds
>>>
>>> http://www.astro.caltech.edu/~tmao/73.37BLD.AVI
>>>
>>> Tyson Mao
>>> Astrophysics '06
>>> California Institute of Technology
>>>
>>>
>>>
>>>   SPONSORED LINKS
>>>         Jigsaw puzzle game   Free puzzle inlay games
> Educational
>>> game and puzzle     Word puzzle game   Kid puzzle game   Puzzle
> games
>>>
>>> ---------------------------------
>>>   YAHOO! GROUPS LINKS
>>>
>>>
>>>     Visit your group "speedsolvingrubikscube" on the web.
>>>
>>>     To unsubscribe from this group, send an email to:
>>>  [EMAIL PROTECTED]
>>>
>>>     Your use of Yahoo! Groups is subject to the Yahoo! Terms of
>>> Service.
>>>
>>>
>>> ---------------------------------
>>>
>>>
>>>
>>>
>>>             
>>> ---------------------------------
>>>  Yahoo! Acesso Grátis
>>> Internet rápida e grátis. Instale o discador agora!
>>>
>>> [Non-text portions of this message have been removed]
>>>
>>>
>>>
>>>
>>> Yahoo! Groups Links
>>>
>>>
>>>
>>>
>>>
>>>
>>
>
>
>
>
>
>
>
> Yahoo! Groups Links
>
>
>
>
>
>
>



 
Yahoo! Groups Links

<*> To visit your group on the web, go to:
    http://groups.yahoo.com/group/speedsolvingrubikscube/

<*> To unsubscribe from this group, send an email to:
    [EMAIL PROTECTED]

<*> Your use of Yahoo! Groups is subject to:
    http://docs.yahoo.com/info/terms/
 


Reply via email to