#### not_kevin

##### Member
^ Not taking into account that you save blocks during (non parity) CP almost every time - which probably lowers the average EP twist count - and not taking into account the look-ahead advantage of non-parity CP, especially if you have blocks (Maybe I'm wrong here, but that's how I would intuitively argue)
Yeah, the context of the fb post was analyzing the move-count efficiency of CPP versus regular CP+EP.

^ Not taking into account that you save blocks during (non parity) CP almost every time - which probably lowers the average EP twist count - and not taking into account the look-ahead advantage of non-parity CP, especially if you have blocks (Maybe I'm wrong here, but that's how I would intuitively argue)
Correct. The first factor is included in the 10.181 number later in the post (among other tricks - the effects of just preserving blocks in CP would be much less pronounced). The lookahead factor for parity cases doesn't mean as much (I lookahead just fine with parity CP) although I'd suspect that preserving blocks probably saves 1-2 twists on average just like with the nonparity cases.

Anyway, the numbers for that part are based on things I actually do in solves - I could calculate what it would look like optimally for parity cases, but that doesn't necessarily mean that anyone has the recognition to do the optimal thing every time. It takes some fancy recognition tricks for me to be able to see and force good cases as much as I do, and I'm not sure anyone's put in that much work for the parity cases.

Last edited:

#### Lid

##### Member
Here are some numbers from my PBL project:

 twists no parity parity total 0 1 1 3 6 6 4 6 6 5 51 51 6 178 178 7 387 6 393 8 283 48 331 9 56 250 306 10 398 398 11 224 224 12 42 42 total 968 968 1936 avg 7.068 9.942 8.505
[TR="colspan:4"] optimal twists for all PBLs [/TR]
 moves no parity parity total 0 1 1 7 1 1 8 1 1 9 6 6 10 2 2 11 7 7 12 3 3 13 25 25 14 13 13 15 70 70 16 47 47 17 116 4 120 18 172 172 19 165 29 194 20 90 28 118 21 133 81 214 22 73 142 215 23 31 190 221 24 8 127 135 25 4 151 155 26 119 119 27 68 68 28 28 28 29 1 1 total 968 968 1936 avg 18.510 23.698 21.104
[TR="colspan:4"] optimal moves for all PBLs [/TR]
And here is a small list of the really short ones:

3 twists: op/op, Na/Na, Nb/Nb, Na/Nb, Nb/Na, pN/pN
7 twists parities: op/Na, Na/op, op/Nb, Nb/op, H/pN, pN/H

7 moves: Na/Na
8 moves: J/J
9 moves: op/op, J/Na, Na/J, Na/Nb, Nb/Na, pN/pN
10 moves: J/L, L/J
12 moves: -/J, J/-, L/L

and the lonely long one:
29 moves: Ra/Q

(p=pure corner swap)

.. and move numbers may not be 100% due to that I may not have found the optimal starting alignment for all cases

Last edited:

#### FailCuber

##### Member
Im a noob at squan. Can you guys tell me all the up to date resources? I dont know how to solve one so I want a good tutorial on how to solve on too.

#### Isaac Lai

##### Member
Here are some numbers from my PBL project:

 twists no parity parity total 0 1 1 3 6 6 4 6 6 5 51 51 6 178 178 7 387 6 393 8 283 48 331 9 56 250 306 10 398 398 11 224 224 12 42 42 total 968 968 1936 avg 7.068 9.942 8.505
[TR="colspan:4"] optimal twists for all PBLs [/TR]
 moves no parity parity total 0 1 1 7 1 1 8 1 1 9 6 6 10 2 2 11 7 7 12 3 3 13 25 25 14 13 13 15 70 70 16 47 47 17 116 4 120 18 172 172 19 165 29 194 20 90 28 118 21 133 81 214 22 73 142 215 23 31 190 221 24 8 127 135 25 4 151 155 26 119 119 27 68 68 28 28 28 29 1 1 total 968 968 1936 avg 18.510 23.698 21.104
[TR="colspan:4"] optimal moves for all PBLs [/TR]
And here is a small list of the really short ones:

3 twists: op/op, Na/Na, Nb/Nb, Na/Nb, Nb/Na, pN/pN
7 twists parities: op/Na, Na/op, op/Nb, Nb/op, H/pN, pN/H

7 moves: Na/Na
8 moves: J/J
9 moves: op/op, J/Na, Na/J, Na/Nb, Nb/Na, pN/pN
10 moves: J/L, L/J
12 moves: -/J, J/-, L/L

and the lonely long one:
29 moves: Ra/Q

(p=pure corner swap)

.. and move numbers may not be 100% due to that I may not have found the optimal starting alignment for all cases
What's a Q perm?

#### Lid

##### Member
Here are some alternative EPs I found for the M2 O/op & the 2xCP H/U

O+/op ODD twist
1,0/6,0/5,-1/-3,0/1,1/-3,0/-1,-1/0,1 [7|18]
O-/op ODD twist
0,-1/1,1/3,0/-1,-1/3,0/-5,1/6,0/-1,0 [7|18]

H/U+ ODD twist
1,0/2,-1/-2,1/2,-1/3,0/-3,0/-2,1/3,0/-3,0/5,0 [9|23]
H/U- ODD twist
1,0/3,0/-3,0/2,-1/3,0/-3,0/-2,1/2,-1/-2,1/5,0 [9|23]

Some PBLs:
Those can be forced to good U/U, but they save 3 twists.
1,0/-1,2/-2,-2/6,0/-1,-1/-2,1/-1,0 [6|17] Rb/Ra
0,-1/0,3/-2,-2/3,-3/-1,-1/0,3/0,1 [6|16] Ra/Rb

Let me know if there are any other PBLs you like to get an alg for.

The first two are pretty much standard, but they use 1,0/5,-1/6,0 in place of one of the M2s. I've actually used this for a while as a quick way to swap E slice on algs that use M2 (H, Z, O/opp, O/O, etc).

I gotta try those H/U algs when I get home, though.

#### TMarshall

##### Member
Thoughts on the vandenbergh method

While I think vandenbergh method is capable of sub 10 global averages, I do think it will have its limitations for times closer to sub 9. Here are some thoughts on how it could be improved. First off, the next reasonable step would be to combine two of the steps (CS, CO, EO, CP, EP) while EP and CP would probably be the best place to combine, the number of algs makes this close to impossible in my mind. The next place to combine, EO and CP would be a lot of algs, but nowhere near as many algs as PBL (I think). Next, combining CO and EO is just known as AO, and I think that is the most reasonable place to combine. While it is ~180 algs, most of the algs are very short. However, from my experience with this, it can be somewhat hard to recognize. So, I think it would be possible to do CS+AO in one look, by using something similar to what Mike Hughey did for sq1 bld, just knowing where the pieces end up and so being able to do CS,Co, and EO in one look. Back to EP and CP, one thing that I noticed I was doing intuitively was after seeing a certain PLL case so many times, you start to generally know what EP case you'll have (I'm sure all of the faster sq1 solvers already do this) Therefore, I would just finish this off and learn what PLL case yields what EP case (and the angle at which you get the PLL so that you know how to AUF/ADF) so that you can one look CP and EP. If you were able to do all of the things mentioned, you could solve the sq1 in 2 looks every time. However, I think this can still be improved. By using CS+parity, you could probably drop ~1 second on your times. However, you would have to know how 180 (plus mirrors) CS algs affect the corners and edges so you could do AO. However, even if you eliminate parity that early, there are still some PBL cases that if you just do normal CP+EP, are downright nasty (stuff like M-Ca, which I think will give you W-O for EP) Therefore, for the really nasty cases, you could learn some PBL algs for it. This would probably only be about 20 PBLs, but you could always learn more.

In conclusion, I think the best vandenbergh variant would be CS+parity and AO in one look, and then CP+EP or PBL. However, this would also be quite a lot of algs and you would have to put a massive amount of time and effort just to be able to learn all the algs/cases for this method. I think the alg count would be somewhere around 260 algs, plus figuring out how 180 CS cases effect your pieces. On top of that, you'd have to learn how to tell if you have parity during CS, but I don't think that is too bad.(I would ask Jabari if he'd be willing to learn all these algs, but he already told me that he hates Sq1 ) I think this is doable, though because if you learned one alg or CS case a day, which is very doable, you would learn this full method in about 16 months. Also, a lot of you probably know lots of non-parity EPs already, and so you could reduce the alg count greatly.

#### Sam N

##### Member
Thoughts on the vandenbergh method

While I think vandenbergh method is capable of sub 10 global averages, I do think it will have its limitations for times closer to sub 9. Here are some thoughts on how it could be improved. First off, the next reasonable step would be to combine two of the steps (CS, CO, EO, CP, EP) while EP and CP would probably be the best place to combine, the number of algs makes this close to impossible in my mind. The next place to combine, EO and CP would be a lot of algs, but nowhere near as many algs as PBL (I think). Next, combining CO and EO is just known as AO, and I think that is the most reasonable place to combine. While it is ~180 algs, most of the algs are very short. However, from my experience with this, it can be somewhat hard to recognize. So, I think it would be possible to do CS+AO in one look, by using something similar to what Mike Hughey did for sq1 bld, just knowing where the pieces end up and so being able to do CS,Co, and EO in one look. Back to EP and CP, one thing that I noticed I was doing intuitively was after seeing a certain PLL case so many times, you start to generally know what EP case you'll have (I'm sure all of the faster sq1 solvers already do this) Therefore, I would just finish this off and learn what PLL case yields what EP case (and the angle at which you get the PLL so that you know how to AUF/ADF) so that you can one look CP and EP. If you were able to do all of the things mentioned, you could solve the sq1 in 2 looks every time. However, I think this can still be improved. By using CS+parity, you could probably drop ~1 second on your times. However, you would have to know how 180 (plus mirrors) CS algs affect the corners and edges so you could do AO. However, even if you eliminate parity that early, there are still some PBL cases that if you just do normal CP+EP, are downright nasty (stuff like M-Ca, which I think will give you W-O for EP) Therefore, for the really nasty cases, you could learn some PBL algs for it. This would probably only be about 20 PBLs, but you could always learn more.

In conclusion, I think the best vandenbergh variant would be CS+parity and AO in one look, and then CP+EP or PBL. However, this would also be quite a lot of algs and you would have to put a massive amount of time and effort just to be able to learn all the algs/cases for this method. I think the alg count would be somewhere around 260 algs, plus figuring out how 180 CS cases effect your pieces. On top of that, you'd have to learn how to tell if you have parity during CS, but I don't think that is too bad.(I would ask Jabari if he'd be willing to learn all these algs, but he already told me that he hates Sq1 ) I think this is doable, though because if you learned one alg or CS case a day, which is very doable, you would learn this full method in about 16 months. Also, a lot of you probably know lots of non-parity EPs already, and so you could reduce the alg count greatly.
a lot of what you have stated has already been done. CO+EO = OBL. EO+CP = PBL etc. There are a lot of people who have contributed and thought of these things before, but it's great that you're thinking about possible adjustments.

#### TMarshall

##### Member
a lot of what you have stated has already been done. CO+EO = OBL. EO+CP = PBL etc. There are a lot of people who have contributed and thought of these things before, but it's great that you're thinking about possible adjustments.
Ya i was sure others had thought of this, but I'm fairly certain PBL and OBL/AO have not been developed in full. The point of my post was to just put everything together into an "ultimate" method

#### Sam N

##### Member
Ya i was sure others had thought of this, but I'm fairly certain PBL and OBL/AO have not been developed in full. The point of my post was to just put everything together into an "ultimate" method
when it comes to PBL, all the cases have been done as seen here: http://www.cubezone.be/square1eocp.txt

If you look on some of the older threads you can find a lot of good information on these topics.

#### TMarshall

##### Member
when it comes to PBL, all the cases have been done as seen here: http://www.cubezone.be/square1eocp.txt

If you look on some of the older threads you can find a lot of good information on these topics.
Thanks for the list! Do you know if full AO/OBl is done? All I could find is AO for the 1 slice CO cases.

#### Sam N

##### Member
Thanks for the list! Do you know if full AO/OBl is done? All I could find is AO for the 1 slice CO cases.
Here is a link to Andrew Nelson's Page on OBL.

http://andrewknelson.com/sq1ao.html

I can't confirm that all the cases have been done, but his page has a lot of the nice cases. You would have to talk it over with him to know if all the cases have been done.
His page is a great place to start learning OBL / AO, so I highly recommend using it if you want to learn more about it.

Last edited:

#### TMarshall

##### Member
Here is a link to Andrew Nelson's Page on OBL.

http://andrewknelson.com/sq1ao.html

I can't confirm that all the cases have been done, but his page has a lot of the nice cases. You would have to talk it over with him to know if all the cases have been done.
His page is a great place to start learning OBL / AO, so I highly recommend using it if you want to learn more about it.
Thank you! I'll definitely be learning those. Also, what should my splits be for sub 13? (I don't do any fancy stuff, just standard CS, CO, EO, CP, EP). I know splits are kinda hard to give on sq1 because of parity and stuff, but I need to figure out where my weak points are.

#### Sam N

##### Member
Thank you! I'll definitely be learning those. Also, what should my splits be for sub 13? (I don't do any fancy stuff, just standard CS, CO, EO, CP, EP). I know splits are kinda hard to give on sq1 because of parity and stuff, but I need to figure out where my weak points are.

I can't actually give any advice until you tell me what your splits are currently. Everyone is different when it comes to solving.

Last edited:

#### Sam N

##### Member
CS: 2-3
CO:1-2
EO:2-3
CP:1-2
EP:4-6
Your Cubeshape, Corner Orientation, Edge Orientation, and Corner Permutation all seem fine to me. EP is usually the barrier when it comes to getting sub 13 averages. How many EP cases do you know involving parity?

#### TMarshall

##### Member
Your Cubeshape, Corner Orientation, Edge Orientation, and Corner Permutation all seem fine to me. EP is usually the barrier when it comes to getting sub 13 averages. How many EP cases do you know involving parity?
I think I know around 50 or so. However, I think my fingertricks for some of the cases aren't that great, so I'll just drill the ones I already know and learn some more ones for annoying cases. Thanks for the advice!