aboutsummaryrefslogtreecommitdiff
path: root/utils/FORMAT.txt
diff options
context:
space:
mode:
Diffstat (limited to 'utils/FORMAT.txt')
-rw-r--r--utils/FORMAT.txt35
1 files changed, 0 insertions, 35 deletions
diff --git a/utils/FORMAT.txt b/utils/FORMAT.txt
deleted file mode 100644
index 5bfb01e..0000000
--- a/utils/FORMAT.txt
+++ /dev/null
@@ -1,35 +0,0 @@
1The functions readcube() and writecube() use different formats to read
2and write a cube to text. Not all formats are supported for both input
3and output.
4
5# H48 - standard format for h48 (read, write)
6
7Each edge is represented by two letters denoting the sides it belongs to
8and one number denoting its orientation (0 oriented, 1 mis-oriented).
9Similarly, each corner is represented by three letters and a number
10(0 oriented, 1 twisted clockwise, 2 twisted counter-clockwise).
11Edge orientation is relative to the F / B axis, corner orientation is
12relative to the U / D axis.
13
14The pieces are ordered such that the solved cube looks like this:
15
16UF0 UB0 DB0 DF0 UR0 UL0 DL0 DR0 FR0 FL0 BL0 BR0
17UFR0 UBL0 DFL0 DBR0 UFL0 UBR0 DFR0 DBL0
18
19Whitespace (including newlines) between pieces is ignored when reading
20the cube, and a single whitespace character is added between pieces
21when writing.
22
23The cube after the moves R'U'F looks like this:
24
25FL1 BR0 DB0 UR1 UF0 UB0 DL0 FR0 UL1 DF1 BL0 DR0
26UBL1 DBR1 UFR2 DFR2 DFL2 UBL2 UFL2 DBL0
27
28# SRC - representation of the object in C code for cube_array (write)
29
30The exact format depends on the internal cube representation. It is
31guaranteed that, if OUT is the output in this format, the line
32
33cube_t cube = OUT;
34
35is interpreted correctly by h48.

Generated with cgit - Back to sebastiano.tronto.net