[Help Thread] 4x4 Discussion

[mencarikebenaran]

4x4 logic :
which is faster ?
50.50 no parity
54.43 OLL parity

 

[xyzzy]

4x4 logic :
which is faster ?
50.50 no parity
54.43 OLL parity

Made me think of a funny hypothetical scenario:
"Yeah, my average of 5 may have been 1 second slower, but I also had double parity on all five solves while the other guy had PLL parity only once out of five solves! I totally deserve to have gotten 1st place instead!"

 

[mencarikebenaran]

Made me think of a funny hypothetical scenario:
"Yeah, my average of 5 may have been 1 second slower, but I also had double parity on all five solves while the other guy had PLL parity only once out of five solves! I totally deserve to have gotten 1st place instead!"

sorry i just realised that i posted wrong time.
that time is my actual solve.

what i mean is . lets say for example if u got :
50 seconds no parity
50 seconds with OLL parity
50 seconds with PLL parity
50 seconds with OLL and PLL parity
the time is same, but ....

 

[Timona]

sorry i just realised that i posted wrong time.
that time is my actual solve.

what i mean is . lets say for example if u got :
50 seconds no parity
50 seconds with OLL parity
50 seconds with PLL parity
50 seconds with OLL and PLL parity
the time is same, but ....

Parity isn't separate from the solve. It still counts as the time so they're all the same, in my opinion.

 

[Abram Grimsley]

sorry i just realised that i posted wrong time.
that time is my actual solve.

what i mean is . lets say for example if u got :
50 seconds no parity
50 seconds with OLL parity
50 seconds with PLL parity
50 seconds with OLL and PLL parity
the time is same, but ....

Since 4x4 is a luck-based event, I would say that 50 seconds with oll and pll parity is faster, because; if you think about it, your solve was so good, if you hadn't gotten oll and pll parity, it would have been a sub-50 solve.
I could be wrong, but that is what I think.

 

[Thom S.]

If you can solve at a consistent speed, meaning you have done like 50+ solves in your life at that event, then you will solve at a consistent speed - your average speed.
If you get double parity in your solve, you got unlucky there, if you get no parity, you got lucky. But, since those 2 solves have the same time and you got parity on one of them, that undoubtedly means that you got luckier during another part of the solve, therefore cancelling out the luck on that solve and with other solves of that same speed.
If I were to get a totally average F2L and my COLL is my worst one, my solve will be slower than average, would I have gotten good F2L and my worst COLL, I would be on average and my luck cancelled out. Were both lucky, I would get a better time.
Transfer this to parity. A solve with parity isn't faster just because you got another 2-4 seconds of algorithm, the whole solve isn't slower because you got lucky.
This makes sense more at 6 and 7, but is applicable on 3, 4 and 5 as well.

 

[Abram Grimsley]

If you can solve at a consistent speed, meaning you have done like 50+ solves in your life at that event, then you will solve at a consistent speed - your average speed.
If you get double parity in your solve, you got unlucky there, if you get no parity, you got lucky. But, since those 2 solves have the same time and you got parity on one of them, that undoubtedly means that you got luckier during another part of the solve, therefore cancelling out the luck on that solve and with other solves of that same speed.
If I were to get a totally average F2L and my COLL is my worst one, my solve will be slower than average, would I have gotten good F2L and my worst COLL, I would be on average and my luck cancelled out. Were both lucky, I would get a better time.
Transfer this to parity. A solve with parity isn't faster just because you got another 2-4 seconds of algorithm, the whole solve isn't slower because you got lucky.
This makes sense more at 6 and 7, but is applicable on 3, 4 and 5 as well.

Good point.

 

[mencarikebenaran]

how to solve H perm on 4x4 :

 

[Garf]

how to solve H perm on 4x4 :

Why is that so weird to think about...?

 

[Thom S.]

how to solve H perm on 4x4 :

Great and both of them are considerably slower

 

[Timona]

Which is better and faster?
- recognising that you have PLL + parity, and doing the parity from any angle, not regarding what PLL you get afterwards
OR
- Recognising that you have PLL + parity, finding and angle to do a suitable PLL from, and doing said PLL so you end up with opposite swap PLL Parity

 

[NigelTheCuber]

Which is better and faster?
- recognising that you have PLL + parity, and doing the parity from any angle, not regarding what PLL you get afterwards
OR
- Recognising that you have PLL + parity, finding and angle to do a suitable PLL from, and doing said PLL so you end up with opposite swap PLL Parity

First, I think. Less to think about.

 

[Thom S.]

Which is better and faster?
- recognising that you have PLL + parity, and doing the parity from any angle, not regarding what PLL you get afterwards
OR
- Recognising that you have PLL + parity, finding and angle to do a suitable PLL from, and doing said PLL so you end up with opposite swap PLL Parity

Easier is the first one, but will always be eary as you can end up with better or worse PLLs. Also you
Recognise PLL
Recognise Parity
Execute Parity
Recognise PLL again
Execute PLL
On 2 you recognise Once. Therefore faster.
There should be a list either on the Wiki or on Cubeskills about this issue and which Case gets which PLL from which angle.

 

[mencarikebenaran]

Which is better and faster?
- recognising that you have PLL + parity, and doing the parity from any angle, not regarding what PLL you get afterwards
OR
- Recognising that you have PLL + parity, finding and angle to do a suitable PLL from, and doing said PLL so you end up with opposite swap PLL Parity

i dont hate G perm, but its really long and make my time slower
there is a PLL parity case which is : Jb perm + parity, the case looks like T perm but with adjacent edges swapped. also the mirror case , i solve this by doing Ja perm first then parity

 

[jfitch]

During last 2 edges using yau i came across this case. Is there a way to solve this more efficiently than flip Uw flip Uw'?

View attachment 19156

I use redux, and I'm not sure what alg you mean by 'flip', but I do this when I get L2D:
Setup from your picture: F' U' F R'
Solve: u' R U' R' F' U2 F u
Should work for your case.

 

[Timona]

Help! I use a method I call Yauduction, which is redux with 323 edge pairing, and I average 1:20. I want to switch to Yau, but everytime I try I get something like a 1:45 avg. Its all in the yau centers w/ the cross edges. Help!

Practice more, watch JPerm's playlist on getting good at 4x4. It's all in the practice, you cant expect to learn something totally different from what you do normally and immediately be good at it.

 

[mencarikebenaran]

i hate doing slice moves

which is faster parity alg ?

Rw2 R2 U2 Rw2 R2 Uw2 Rw2 R2 Uw2

or

Rw2 F2 U2 Rw2 R2 U2 F2 Rw2 ???

 

[Timona]

i hate doing slice moves

which is faster parity alg ?

Rw2 R2 U2 Rw2 R2 Uw2 Rw2 R2 Uw2

or

Rw2 F2 U2 Rw2 R2 U2 F2 Rw2 ???

Ive never personally tried the second one but the first one is more moves

 

[CUBING08]

Hi I am sub 1 min 30 second at 4x4, how to get faster

 

[PiKeeper]

i hate doing slice moves

Get better at slice moves