4 ms·
Unable to fully parse what you are trying to express. > the total state is significantly reduced. The minimal "state space" of a rubiks cube is a constant val
by dsfiof 9mo ago
Unable to fully parse what you are trying to express.
> the total state is significantly reduced.
The minimal "state space" of a rubiks cube is a constant value. Any "reduction" would imply the model being reduced was inefficient.
On the topic of cool "alternative" views of rubiks I recently saw this and thought it was novel.
https://old.reddit.com/r/gifs/comments/z3okyv/the_only_way_to_simultaneously_see_all_sides_of_a/ https://old.reddit.com/r/gifs/comments/z3okyv/the_only_way_t...
- wowczarek 9mo agoThat link. This is a Celtic Knot and 92 is half of 99. I had to.
- phkahler 9mo ago>> > the total state is significantly reduced. >> The minimal "state space" of a rubiks cube is a constant value. The article is about solving a cube with software. Software typically represents both the orientation AND position of 20 (or 26) pieces. Orientation might be enumerated so it can be represented by number 1-24 or 0-23 as software tends to do. It could also be represented by a set of Euler angles for each piece. Position is could be enumerated since there are only 20 positions or it could be a vector indicating the piece center relative to the origin. There is a certain amount of data needed to represent the cube in a useful way. Apparently some people store the color (1-6) for each face for a total of 6x9 = 54 numbers each from 1-6. Any of these representations has more possible states than an actual cube because you can encode position that are not possible to achieve on a real cube (solved with a single corner rotate for example). My point is that the 20 orientations are enough without the positions if you're trying to track position AND orientation like the linked article does. The positions can be recovered from the orientations.