[UWR] 128x128x128 solve

[qqwref]

First part later tonight (let's say 7pm Eastern). I'm starting with edges, which is roughly an hour, and then I'll move onto clearing the white center.

Which program do you use to emulate that cube ? Wow

IsoCubeSim

However: It would be a good idea to have a mic so you can talk to people in the chat.

I can type stuff, it doesn't waste much time (and I don't usually get that many people in chat when I'm streaming stuff ). And since I don't talk often normally, you'd just be hearing clicking most of the time. Probably better to just let people listen to whatever they want.

Can you try the cube in a cube^128?

If you mean a super-supercube, that would take about 21.5 times as long as this one (and there's no sim that can handle anything even remotely close to that anyway). If you just mean the pretty pattern, I could do this one and a few others at the end, sure

Good luck. Hope to have not so many parities

Hehe, don't worry, I do all the OLL parities at once The algorithm I use is r2 U2 r' U2 r' [flip UB] r' [unflip UB].

Would it be possible to see some statistics during the solve? e.g. time for first half of white centres

Sure, I'll keep track of the time at each major section.

Gonna be funny how unproportional the sections will be...

Centers: 10 hours
Edges: 29.9 hours
3x3: Few minutes max.

More like:
Edges: 1 hour
Centers: 39 hours

 

[JasonDL13]

http://www.d-e-f-i-n-i-t-e-l-y.com/

I blame my auto correct in chrome http://prntscr.com/534kty

 

[Randomno]

I blame my auto correct in chrome http://prntscr.com/534kty

That's defenitely wrong.

 

[atouchofgeek]

That's some determination, atleast you'll be able to say you did it when it's over!

 

[ComputerGuy365]

Good luck mate.

 

[AlGoreRhythm]

Quote Originally Posted by JasonDL13
I blame my auto correct in chrome http://prntscr.com/534kty

That's defenitely wrong.

Did you spell that wrong as a joke?

 

[qqwref]

Finished edges and 3x3x3 at 1:21:58.421 seconds, in 2951 moves. That's 0.600 moves per second, 1.941 moves per piece, and 3.236 seconds per piece. (The seconds per piece will be much lower later.)

First session done, so far 2:33:22.515 and 7415 moves. About a third of the white center is cleared.

 

[Deathranger999]

Great start Michael! Looking awesome so far.

 

[IRNjuggle28]

Gonna be funny how unproportional the sections will be...

Centers: 10 hours
Edges: 29.9 hours
3x3: Few minutes max.

The centers will take way longer than the edges.

EDIT: should've read thread before posting

 

[Rocky0701]

Did you spell that wrong as a joke?

Lol he defiantly did.

Finished edges and 3x3x3 at 1:21:58.421 seconds, in 2951 moves. That's 0.600 moves per second, 1.941 moves per piece, and 3.236 seconds per piece. (The seconds per piece will be much lower later.)
http://i.imgur.com/9lbYJhD.jpg

First session done, so far 2:33:22.515 and 7415 moves. About a third of the white center is cleared.
http://i.imgur.com/I6lxTaV.jpg

How do you tell each layer apart? It looks impossible to see. Are you able to zoom in on the program?

 

[szalejot]

Finished edges and 3x3x3

Do you start with edges and 3x3?
What kind of method is that?

 

[irontwig]

Do you start with edges and 3x3?
What kind of method is that?

(A type of) cage method.

 

[Randomno]

Finished edges and 3x3x3 at 1:21:58.421 seconds, in 2951 moves. That's 0.600 moves per second, 1.941 moves per piece, and 3.236 seconds per piece. (The seconds per piece will be much lower later.)
http://i.imgur.com/9lbYJhD.jpg

First session done, so far 2:33:22.515 and 7415 moves. About a third of the white center is cleared.
http://i.imgur.com/I6lxTaV.jpg

I think I've seen an image like that.

Oh yeah, a compressed JPEG.

 

[qqwref]

For some reason there were a few null characters in my save and it was breaking when I tried to load the save again (a disturbing amount of the cube was showing as solved because it just stopped reading the stickers partway through). I managed to fix that, and also improved the saving part so it doesn't take forever. Download updated version here. Dunno why this problem never showed up before, but I could have fixed the save thing at any time, I just hadn't looked at the program since mid 2013.

I'm going to be starting the second stream for real soon.

How do you tell each layer apart? It looks impossible to see. Are you able to zoom in on the program?

Yeah, when I do my solve I'm zoomed in a lot. The zoom out is to make it easier for anyone watching the topic to see progress.

Do you start with edges and 3x3?
What kind of method is that?

A cage method It's actually quite optimized and for very large cubes I think it's significantly faster than reduction, and more efficient too unless you are incredible at finding pieces. The description in the 111x111x111 topic is pretty close to what I use, although I have changed some details since then.

 

[brian724080]

How big is your screen?

 

[qqwref]

After the second session, I have finished clearing the white center. Total time 4:33:48.109, and 16367 moves. That means that since edges+3x3x3 I have done moves at 1.166 moves/second. Clearing solves about 63.5% of the white centers (and 1/6 are solved already) so I solved about 7439 additional centers (don't know the exact number) at a rate of about 1.803 moves per piece or about 1.547 seconds per piece.

How big is your screen?

Overall 1680x1050... but I don't fill it all with the cube. I also have stuff like twitch chat open. Having it fullscreen wouldn't save much time since I spend most of the time looking at a single column anyway.

 

[brian724080]

Overall 1680x1050... but I don't fill it all with the cube. I also have stuff like twitch chat open. Having it fullscreen wouldn't save much time since I spend most of the time looking at a single column anyway.

I see, but don't you find it annoying that you can only see so much of the cube?

 

[mark49152]

Just curious, but at what size do you think it becomes more efficient to use the cage approach than centres-first reduction? If you were solving a physical 11x11 or 8x8, what would you use?

 

[qqwref]

I'm dumb so no progress today. Oh well.

I see, but don't you find it annoying that you can only see so much of the cube?

With this method, it doesn't hurt. It also keeps down lag.

Just curious, but at what size do you think it becomes more efficient to use the cage approach than centres-first reduction? If you were solving a physical 11x11 or 8x8, what would you use?

It's hard to tell and it definitely depends on how good someone is on each method. Comparing cage on Iso vs reduction on Iso, cage is faster starting on the 10x10x10; comparing cage on Iso vs reduction on qcube, cage is faster starting on the 12x12x12. For physical cubes I think you'd need a really really big cube for cage to be worthwhile because slice turns are such a pain.

 

[qqwref]

White center solved! Yay!

Total time 7:51:14.623, and 39775 moves. Since clearing I have done moves at 1.976 moves/second. I don't know exactly how many white center pieces were solved since then, but it should be about 5791. That gives me a solving rate of about 4.042 moves per piece (as expected since almost all the new pieces were solved with 4-move commutators) or about 2.046 seconds per piece.