Repository navigation
Stockfish FAQ
Note: Stockfish is a command line program. You may want to use it in your own UCI-compatible chess GUI.
- Log in to Github
- Navigate our Actions
- Click on the first workflow run
- Scroll to the bottom of the page
- Select the corresponding binary
Note: You can also compile from source the latest commit. TODO: Compile from source wiki page
- Intel: 4th Gen and newer.
- AMD: Zen 3 and newer.
- AMD: Zen, Zen+ and Zen 2.
If you are still unsure, download all binaries and run the bench command.
TODO
TODO
TODO
TODO
TODO
TODO
Stockfish may crash if fed incorrect fens, or fens with illegal positions. Full validation code is complex to write, and there is no established mechanism to communicate such an error back to the GUI.
On the other hand, the GUI must carefully check fens. If you find a GUI through which you can crash Stockfish or any other engine, then by all means report it to that GUI's developers.
There is a branch developed with a MPI cluster implementation of Stockfish, allowing stockfish to run on clusters of compute nodes connected with a high-speed network. See https://github.com/official-stockfish/Stockfish/pull/1571 for some discussion of the initial implementation and https://github.com/official-stockfish/Stockfish/pull/1931 for some early performance results.
Feedback on this branch is welcome! Here are some git commands for people interested to test this MPI/Cluster idea:
- If you don't have the cluster branch yet on your local git repository, you can download the latest state of the
official-stockfish/clusterbranch (See also https://github.com/official-stockfish/Stockfish/tree/cluster), then switch to it with the following commands:
git fetch official cluster:cluster
git checkout -f cluster- After switching to the cluster branch as above, see the README.md for detailed instructions on how to compile and run the branch. TL;DR:
make clean
make -j ARCH=x86-64-modern COMPILER=mpic++ build
mpirun -np 4 ./stockfish benchAlso known as "CPUs". TODO
Also known as "memory". TODO
Counter of iterative deepening loop. Regardless of the name, there is no simple connection to depth.
Also known as "seldepth", is the depth of the deepest principal variation line in the search.
Also known as "MultiPV", "number of lines" or "multiple lines". TODO
TODO
Also known as "TT". TODO
Also known as "Lazy SMP", is the idea of executing the search function on N many threads and share the hash table. This allows for faster filling of the hash table, resulting in a faster and wider search.
The idea of performing consecutive searches at higher depths each time.
Also known as "PV". TODO
The idea of ignoring certain parts of the search tree in order to reduce the amount of time it takes to execute a search.
TODO
TODO
TODO
TODO
TODO
TODO
In order to maximize the efficiency of alpha-beta search, we optimally want to try the best moves first.
Also known as "qSearch". TODO
Also known as "classic", "classical" or "HCE". TODO
Also known as "NNUE". TODO
New commits to stockfish can mostly be categorised in 2 categories:
- Non functional changes
- Functional changes
Changes that don't change the search behaviour, for example:
- Code cleanups
- Comments
- New commands
These change the search behaviour and lead to a different search tree.
Every functional patch (commit) has to be verified by Fishtest, our testing framework.
You can follow the steps described in our Fishtest wiki, to create your first test.
https://github.com/glinscott/fishtest/wiki/Creating-my-first-test