qwertycuber
Regular
Here is my version of that page: http://hem.bredband.net/_zlv_/rubiks/sq1/sq1-shape-depth.html
Thanks, this is exactly what I was looking for.
Follow along with the video below to see how to install our site as a web app on your home screen.
Note: This feature may not be available in some browsers.

Here is my version of that page: http://hem.bredband.net/_zlv_/rubiks/sq1/sq1-shape-depth.html
Also the only reason I can't solve a square 1 without looking at a tutorial is parity. Not the memorization, but even looking at the alg, I still can't do it. Does anyone have any idea why?
http://mzrg.com/js/cubeshape_trainer.htmlAnyone know of a way to generate scrambles for only cube shape, so I can more efficiently get better at cube shape? It'd be nice to not have to do a whole scramble just to practice a step of the solve.
The thing about this is that the hard part of PCS is detecting the parity. Fixing the parity is the easy part. If you understand parity, changing it to solved is the easy part. PCS isn't a set of algorithms; usually to change the parity, you just need to add in one move.Just an idea I think I'm gonna try and wanted throw out into the forums:
For square-1, parity cubeshape is a thing now. The problem with it is it requires a ton of practice and knowing 2 algs for each cubeshape case. Instead, why not detect parity during cubeshape and then use parity CP to eliminate parity. From what I understand CP Parity's big downfall is recognition time so if you know you need to use a parity cp alg from the beginning then it should be pretty close in speed to normal CP. This also gives you the benefit of a backup parity detection step. If you messed up detecting parity in inspection you can still take a second to recognize parity in CP step before executing an alg.
I do think that parity cubeshape is probably going to ultimately be better but I think this may be a good alternative/intermediate step to learning PCS as it practices the detection and only requires learning 8 algs to begin with.
Any thoughts/opinions on this?
Yeah. The main idea behind doing this is it will allow me to practice the parity detection with a failsafe to check for parity again. That way I'm not having to practice and learn too much at once. Eventually I will migrate to PCS.The thing about this is that the hard part of PCS is detecting the parity. Fixing the parity is the easy part. If you understand parity, changing it to solved is the easy part. PCS isn't a set of algorithms; usually to change the parity, you just need to add in one move.
Just an idea I think I'm gonna try and wanted throw out into the forums:
For square-1, parity cubeshape is a thing now. The problem with it is it requires a ton of practice and knowing 2 algs for each cubeshape case. Instead, why not detect parity during cubeshape and then use parity CP to eliminate parity. From what I understand CP Parity's big downfall is recognition time so if you know you need to use a parity cp alg from the beginning then it should be pretty close in speed to normal CP. This also gives you the benefit of a backup parity detection step. If you messed up detecting parity in inspection you can still take a second to recognize parity in CP step before executing an alg.
I do think that parity cubeshape is probably going to ultimately be better but I think this may be a good alternative/intermediate step to learning PCS as it practices the detection and only requires learning 8 algs to begin with.
Any thoughts/opinions on this?
Resolving parity during cubeshape is both easier and more efficient. Most people who learn CSP would have a decent knowledge of most cubeshapes and which lead to the other, so learning cubeshape solutions is much easier than learning normal algorithms (like EP or CPP). Furthermore, I don't think that the transition to CSP is difficult or tedious enough to warrant such an intermediate step. The time and effort spent learning CPP could be better spent practising CSP instead.Just an idea I think I'm gonna try and wanted throw out into the forums:
For square-1, parity cubeshape is a thing now. The problem with it is it requires a ton of practice and knowing 2 algs for each cubeshape case. Instead, why not detect parity during cubeshape and then use parity CP to eliminate parity. From what I understand CP Parity's big downfall is recognition time so if you know you need to use a parity cp alg from the beginning then it should be pretty close in speed to normal CP. This also gives you the benefit of a backup parity detection step. If you messed up detecting parity in inspection you can still take a second to recognize parity in CP step before executing an alg.
I do think that parity cubeshape is probably going to ultimately be better but I think this may be a good alternative/intermediate step to learning PCS as it practices the detection and only requires learning 8 algs to begin with.
Any thoughts/opinions on this?