2D Rubik’s Cube solution visualization
twitter.com
twitter.com
"If you want to try solving the Rubik's Cube this way, you should try @roice713's MagicTile. You can choose the Rubik's cube among hundreds of puzzles. The stereographic projection makes it look like the animation in this post."
[1] https://twitter.com/mananself/status/1595132523264167936
Couldn't be further from the truth. The image in the tweet is a huge improvement over the stereographic projection.
1. different-size projected squares are replaced with same-size circles
2. the tweet's image puts the north pole on a corner; the projection on the upthread link puts the north pole on the face.
Keeping the corner at the north pole does make it easier to understand, but it's still a stereographic projection.
here is it in action https://www.youtube.com/watch?v=FCvn9-JvXgY&list=PLKwXjCUFqO...
My favourite one-liner for improving understanding is something roughly like 'solve areas made of pieces, not faces made of stickers'. Very much clearer when you have a cube to take apart and put together in the order you would solve them.
I don't think this is helpful for humans solving, but for computers it largely takes position out of it. Position does determine which pieces are rotated by any given move though.
And congrats on the records! I've managed to get just below the minute mark a handful of times and remain in complete awe of anyone sub 60 seconds!
Regardless, none of that takes away from the nifty 2D projection technique!
Rubik's Cube solution unlocked by memorising 3915 final move sequences[0].
> For the first time, a speedcuber has demonstrated a solution to the Rubik’s cube that combines the two final steps of the puzzle’s solution into one
[0] https://www.newscientist.com/article/2334632-rubiks-cube-sol...
More efficient in terms of rotations necessary to solve the cube.
Get a faster computer and a larger cube, the trade-off is likely worth it. A rubik's cube isn't such an intractable problem, I doubt a computer can't solve it faster than a human: in the worst case, they can rely on the same algorithm. Then, they can try to find shortcuts or just shorter paths.
I always thought minimizing the number of moves was the goal, hence "more efficient" made sense to me too.
https://piaille.fr/@Mnaudin/109389968985022395
It's a really poor representation, for specific reasons:
- it doesn't convey how the corner and edge colors are constrained into moving together, due to being mounted on the same cube piece.
- doesn't convey how the center face pieces stay in place relative to each other.
- certain rotations "cheat": the dots dance around, not staying on their orbit tracks.
It is not a 3x3x3x3 but 2x2x2x2.
It looks like Melinda (the inventor) have made them easier to obtain. back when I got one, 3D printed parts, magnets, and coating all came from different sources, but absolutely worth it, they are very unique and work well.
I'm now on the waiting list for the next batch (couple of weeks to months), and apparently the new injection moulded version is way better, and a lot cheaper!
Here are the links I used back in 2018:
https://www.shapeways.com/product/965KNUESR/melinda-s-2x2x2x...
http://www.gaussboys.com/store/index.php/catalogsearch/resul...
The way to learn path finding problem is to understand how your actions move you through the space you're navigating.
One of the most effective ways to learn these relationships is to work backwards.
Starting from the goal, take a step away, then step back. Then take two steps away, then those steps back. Then take different steps away and steps back.
As you move farther and farther from the goal you get an explosion of options that quickly requires deduction of strategies over memorization of all paths back to the goal.
This can help ground learning the well known techniques for cube solving.
This visualization might help with that process, but just playing solutions from start to finish (IMO) doesn't.
I do have my own 2d view of the rubics cube there. Was fun to watch the squares jump around. :D
Something that helped me was [1]. It took me from being someone who could not solve at all, to actually being quite good-- in the 13-20 second range. The beginner method listed on the site can easily put you in the sub-minute territory.
> Q: I Added you as a friend but you didn't accept. WHY DO YOU HATE ME?
> A: I dont accept any friend invites. But maybe I still hate you, who knows?
I bought a rubik's cube when my son was born, because I wanted something to play that was not my phone while he was on my lap. 3 years later I'm able to complete one face in like 5 min consistently. still a long way to solve it, new techniques to discover and hours of play in sight. yay!
And it's almost impossible to do it without taking notes on paper or computer. (If that were doable, their wouldn't be so many walkthroughs). Solving the cube is a hard applied group theory "homework" problem.
This video explains the principles of solving a Rubik's cube on your own.
You're treating it as a puzzle to solve. But once you learn how to solve it, it ceases to be a puzzle and it becomes a really fun fidget toy. Seeing how fast you can solve it is enjoyable and gives your fingers some great dexterity exercise. I have one on my desk and when I want to take a break from coding I'll scramble it up and fidget around with it for a bit.
If you are interested in optimizing, there are an infinite numbers of axes you can work on to solve faster.
First, there are several general approaches, although realistically, only two (CFOP, Roux).
Each of these methods have phases which you can practice and improve on separately, A lot of them require simple memorization (muscle memory for the most part) but all of them at some point contain a certain level of intuition and pattern recognition (e.g. lookahead), and for that, the only limit is your brain.
It's a fascinating puzzle with neverending interest, at least for me (I solve in average around 25 seconds).
despite not being able to see all sides of the cube, it's surprisingly easy to solve on, as you essentially see the same stickers that you would in real life.
there is even an IRC based version!
and an explanation of the notation: https://jperm.net/3x3/moves
You got 26 cubes in 3D space that need to go to their correct locations. They can move in 3 axis. They are color coded for recognition.
I think anyone is able to solve the first 2 layers intuitively. Just start by following one of those 26 little cubes and see how it moves about.
Like someone saying “less space than a nomad. Lame.”
It's more of a worn-out trope by this point and better skipped. Just sneerfully flag lame comments.
Dark [Rubik's] Magic that they are.
I agree with the other commenter that a normal 3D cube feels much more intuitive and simple. I guess it's just personal preference/thinking style.
But it is not one of the cubes that need to go to their correct locations. The center cube is not moved by any operation on the cube; it is always in its correct location.
(At least, that's true of the 26 outer cubes. You can't get them all into place without simultaneously aligning them correctly. I don't actually know if correct alignment of the center cube is also required, but it'd be my first guess.)
Nobody believes there are invisible cubes outside the Rubik's cube. That's not the same logic; that's you trying and failing to imagine a problem with the idea that cutting a cube into three parts along each of its three axes will generate a hidden central subcube.