Roux-breaker? The YruRU method

I am having trouble with the CP part. I have no idea what i am doing or what CP stands for. Every other part of the method i'm golden in. I just need help with CP.
CP stands for “corner permutation.” You basically put all of the corners in their respective places, but they don’t necessarily have to be oriented correctly.
 
This method doesn't have a dedicated discord group yet; but there is now a YruRU channel on the Mehta discord. In the future if there is sufficient demand, we will have a separate discord group for YruRU as well, which I will update here with the invite link. Till then, if interested, please join the Mehta discord.
You can have the discord link in your signature. The SS Forum can be changed in settings.
 
I had a method based on a similar concept of CP before learning about this much more optimal (and slightly older) method.

1. EO 223
2. CP using only one algorithm (not optimal)
3. 2 gen

The cube can be reduced as such:
scrambled <R, L, U, D, F, B>
EO 223 <R, L, U>
CP <R, U>
2 gen <1>

One can see that both methods reduce to 2 gen, but using different steps

EO 223 comes from petrus, solving EO and every piece but the ones in R or U, this step can be done with a 2x2x2 in LBD, EO using free F face, followed by square in front.
CP can only be done using one algorithm when the swap is known and set up is done, I usually solve D corner permutation, then match either 2 or 4 U corners to their E slice edges, then swapping the remaining two un-matched corners with j perm (obviously there are better algs).
2 gen is preferably F2L + 2GLL, though I also find F2L + OCLL + EPLL fairly efficient.

The only problem I see so far is the EO step of the EO 223; EO is usually recognized with a long inspection, never in the middle of a solve.
Other problems like inefficient CP can be solved with better and more algs.

Both methods have their strengths, but I think YruRU still stands higher with better research and more experienced cubers using it.
I mean I'm only sub 25 and barely sub 1 one handed.
 
Hey @Devagio ,

In the About section on your YruRU method, you talk about another potential approach (after FBpEO) that you shot down:

The second way is to reduce the moveset to M-U, i.e. continue like Roux and make a second block; but since CMLL will only be 7 algorithms, we can combine CMLL with second block. This requires 108 algorithms (54 if we are allowed to do M moves before commencing the algorithm) which are all short and [r, R, U]-gen. I tested out both approaches by generating all algorithms, and developed both ideas, till I came across a way to do partial edge orientation during the extension of 1x1x3 to 1x2x3. Also, the extension when applied all by itself is quite inefficient. Thus, unless there was a way to plan CP and FB both in inspection, I concluded that the second approach would not work as good as the first one. [...] The second approach, I named YRoux, because it sounds similar enough and it essentially borrows from Roux.

Do you have any of these YRoux algs you generated? (You can assume M setup moves are allowed or disallowed-- whichever is easier.)

Id be interested in checking such a method out...

Thanks,
Tim.
 
I think this is what you're talking about. Images aren't working so if you have the time plug the algs into ACN and check them out.

Swap + No (Solved)
(U) R U' R' U R U2 R2 U' R U' R' U2 R
(U) R' U2 R U R' U R2 U2 R' U' R U R'
(R U' R')
(U) R U' R' U R U2 R' U' R U2 R' U' R U' R'
(U) R U' R2 U' R2 U' R2 U2 R U' R U' R
(U) R U' R2 U' R2 U' R2 U2 R U' R U' R'
(U2) R' U2 R' U2 R U2 R' U' R2 U R
R U R' U' R U' R2 U2 R U R' U R
(R U' R' U R' U' R U' R' U2 R)
((U')) R U' R' U2 R U' R' U2 R U R'
() R U R' U' R U' R'
(U) R U' R' U R U2 R'
(U) F r U2 R' U' R U' r' F R' F2 R
R U R2 U' R2 U' R2 U2 R
(U) R' U' R2 U' R2 U2 R
()R F' r U R' U' r' F R U' R'
(U') r' U2 R U R' U r F2 r U r' F
(U) R U R' U R2 U' R2 U R U2 R2 U R' U2 R' U R
(U) R U2 R2 U' R U' R' U2 R
R U' R' U R' U2 R U R' U R
(U) R U2 R' U' R U2 R' U' R U' R'
(U') R U R2 U2 R' U R2 U' R' U R2 U R
(U) R U2 R'
(U2) r2 U R' U R U2 r2 U' r U2 r'
R U R' U R2 U' R' U R' U R' U R' U' R
(U') R U' R U2 R' U' R' U R U' R U' R2
(U) R2 U' R2 U R' U2 R2 U R U2 R' U' R
(U) R' U R U2 R' U' R2 U2 R U' R2 U R2
(U) R' U2 R' U R' U' R2 U R' U R2 U2 R'
(U) R' U2 R' U2 R U2 R' U' R2 U R2 U2 R'
(U) R2 U2 R' U R' U2 R U2 R U R' U' R'
(U) R2 U' R U' R2 U2 R2 U R U' R2 U' R
R U' R' U' R U R' U R U2 R'
R U' R2 U2 R U R' U R
(U) R U2 R' U R' U' R U' R' U2 R
(U) R U2 R' U2 R U2 R' U' R U' R'
(U') R2 U R' U R U2 R2 U' R U R'
(U') R2 U R' U R' U' R U R U2 R2
(U) R U' R' U R U' R' U R U2 R'
(U) R U2 R2 U2 R U R' U R
R U' R2 U' R U' R' U2 R
R U R' U' R U R' U' R U' R'
(Note: Multiple algs in a cell are alts for the same case)
 
I think this is what you're talking about. Images aren't working so if you have the time plug the algs into ACN and check them out.
(Note: Multiple algs in a cell are alts for the same case)

What are these? SBLS algs?

The case count (54-108) doesn't match up to your 27.
That's the main thing that has me :confused: :?.
 
I have a proposal. I recently made a post about CP methods. My suggestion was to group all of the CPLine > EOCP 2x2x3 > RB methods into one method and give them a single name. First we had Gilles Roux's idea, then Noah's CP Block 2.0, then Briggs, then C2GR, and finally YruRU. All with essentially the same steps. So how about we have a single method and call it CEOR? This would remove the problem of having various methods that are the same thing except with different CP recognition styles. We also wouldn't be using someone's name when there have been various creators with their own contributions to the general method.

Devagio himself thinks that the method shouldn't be named after a person as seen below.

The only issue I have is calling these method/s “Briggs”. Naming the method after a person is wrong. Call it CEF (for CP-line, EO-223, Finish) for all I care, vote and pick an impersonal name.
Link

YruRU, when it was being presented as a method, was named after himself. So it makes even more sense to use a general name.

I've named the method YruRU [pronounced vaay-roo-roo], short for Yash's r-u-R-U reduction.
Link

CEOR is a perfect name. We have LEOR which does the Left block without CP. Then we have CEOR which is the CP version with the left block. So when you are using this CP method, you would say that you are using CEOR. Not Briggs or YruRU or any other. It isn't necessary to add on to the method which CP recognition method you are using. But if others are curious which recognition method they can use, that information will be available on the wiki page and other sources. We can however have things like CEOR-b which would be the CP version of LEOR-b as PapaSmurf suggested.

PapaSmurf suggested the name CEOR and also to extend the method from not just CPLine but to CPFB > EOCP 2x2x3 > RB. You can read more about the method grouping at the bottom of my main post and also in PapaSmurf's post.
 
I have a proposal. I recently made a post about CP methods. My suggestion was to group all of the CPLine > EOCP 2x2x3 > RB methods into one method and give them a single name. First we had Gilles Roux's idea, then Noah's CP Block 2.0, then Briggs, then C2GR, and finally YruRU. All with essentially the same steps. So how about we have a single method and call it CEOR? This would remove the problem of having various methods that are the same thing except with different CP recognition styles. We also wouldn't be using someone's name when there have been various creators with their own contributions to the general method.

Devagio himself thinks that the method shouldn't be named after a person as seen below.


Link

YruRU, when it was being presented as a method, was named after himself. So it makes even more sense to use a general name.


Link

CEOR is a perfect name. We have LEOR which does the Left block without CP. Then we have CEOR which is the CP version with the left block. So when you are using this CP method, you would say that you are using CEOR. Not Briggs or YruRU or any other. It isn't necessary to add on to the method which CP recognition method you are using. But if others are curious which recognition method they can use, that information will be available on the wiki page and other sources. We can however have things like CEOR-b which would be the CP version of LEOR-b as PapaSmurf suggested.

PapaSmurf suggested the name CEOR and also to extend the method from not just CPLine but to CPFB > EOCP 2x2x3 > RB. You can read more about the method grouping at the bottom of my main post and also in PapaSmurf's post.
Strongly in support of this idea. Will start implementing and promoting it wherever I’m mindful enough to do so.
 
How do we want to handle the merging? I could certainly make the CEOR wiki page and redirect the various pages to there. Then have the various proposers, the steps, recognition methods, a history section, links to the original proposals, and so on.

But what about the YruRU website? Currently it is titled "YruRU Method" and even has all of the steps of a method. Maybe we could convert that into a CEOR website? That would mean adding the other recognition methods. Or do some rewording or restructuring of the site to have it be clear that it is the YruRU recognition method and the recommended method to use it with is CEOR.
 
How do we want to handle the merging? I could certainly make the CEOR wiki page and redirect the various pages to there. Then have the various proposers, the steps, recognition methods, a history section, links to the original proposals, and so on.

But what about the YruRU website? Currently it is titled "YruRU Method" and even has all of the steps of a method. Maybe we could convert that into a CEOR website? That would mean adding the other recognition methods. Or do some rewording or restructuring of the site to have it be clear that it is the YruRU recognition method and the recommended method to use it with is CEOR.
It'll probably be far too much work converting the website to a general CEOR website with all recognition methods; I will make the changes and the rewordings to highlight these changes though.
 
Back
Top