diff options
| author | Sebastiano Tronto <sebastiano.tronto@gmail.com> | 2020-06-21 23:01:57 +0200 |
|---|---|---|
| committer | Sebastiano Tronto <sebastiano.tronto@gmail.com> | 2020-06-21 23:01:57 +0200 |
| commit | 0e8d73bb3edcc8bdff6e3ded442b66f68265059a (patch) | |
| tree | 4f92deb9ace97e79332c0e7ce390b76b81aeaae9 /README.md | |
| parent | 4e359b44ce111b04cc4d2b28033fba4ab4e6e989 (diff) | |
| download | nissy-0e8d73bb3edcc8bdff6e3ded442b66f68265059a.tar.gz nissy-0e8d73bb3edcc8bdff6e3ded442b66f68265059a.zip | |
First push
Diffstat (limited to 'README.md')
| -rw-r--r-- | README.md | 39 |
1 files changed, 38 insertions, 1 deletions
| @@ -1,2 +1,39 @@ | |||
| 1 | # nissy | 1 | # nissy |
| 2 | A Rubik's cube solver and FMC assistant | 2 | A Rubik's cube solver and FMC assistant. |
| 3 | |||
| 4 | ## Just another cube solver? | ||
| 5 | Yes, pretty much. I wanted to write one and I started coding without any | ||
| 6 | specific goal in mind. It is not more efficient than [CubeExplorer](http://kociemba.org/cube.htm), nor it is | ||
| 7 | particularly user-friendly. | ||
| 8 | |||
| 9 | ## But does it do something unique? | ||
| 10 | Yes, actually it does, but only for a very small niche of people. It allows to produce step-by-step solutions using DR | ||
| 11 | ([Thistlethwaite](/https://www.speedsolving.com/wiki/index.php/Thistlethwaite%27s_algorithm)/[Kociemba](https://www.speedsolving.com/wiki/index.php/Kociemba%27s_Algorithm) algorithm) | ||
| 12 | combined with [NISS](https://www.speedsolving.com/wiki/index.php/Fewest_Moves_techniques). This makes it somewhat useful for [FMC](https://www.speedsolving.com/wiki/index.php/Fewest_Moves_Challenge) solvers who want to analyze a scramble and see if they missed something, | ||
| 13 | or what was the optimal way to solve a certain substep at a given point, and so on. | ||
| 14 | |||
| 15 | ## How to use it | ||
| 16 | Check out the help pages in the docs folder. They are also available from | ||
| 17 | within nissy with the command "help". | ||
| 18 | |||
| 19 | I will add more examples and maybe screenshots when I feel like. | ||
| 20 | |||
| 21 | ## Installation | ||
| 22 | For now you have to download all the files and compile the source | ||
| 23 | code yourself. Remember to tell your | ||
| 24 | compiler to use the [C99 standard](https://en.wikipedia.org/wiki/C99). For | ||
| 25 | example, on a Linux system with GCC installed: | ||
| 26 | |||
| 27 | ``` | ||
| 28 | cd path/to/nissy/src | ||
| 29 | gcc -O3 -std=c99 -o ../nissy *.c | ||
| 30 | cd .. | ||
| 31 | ./nissy | ||
| 32 | ``` | ||
| 33 | |||
| 34 | You can also use the script compile.sh in the src folder, which executes that | ||
| 35 | gcc line (with a few extra options). | ||
| 36 | |||
| 37 | ## Tips | ||
| 38 | You can use a tool such as [rlwrap](https://github.com/hanslub42/rlwrap) to allow | ||
| 39 | for infinte command history within nissy! | ||
