Rapfi is a free and powerful Gomoku/Renju (Five in a row) playing engine that analyzes Gomoku/Renju positions and computes the optimal moves. Rapfi engine uses advanced alpha-beta search algorithm with classical and NNUE (Efficiently Updateable Neural Network) evaluation, which achieves more precise evaluation with a significantly larger computation that benefits from the x86-64 vector instructions (such as SSE or AVX).
The engine itself does not contain a graphics user interface (GUI). In order to use it comfortably, you may need a compatible GUI to display the game positions and analysis results and make it easy to input moves. Compatible Gomoku/Renju GUIs include piskvork, qpiskvork and Yixinboard. Yixinboard is mostly recommended at this moment as it supports the full analysis and database functionality.
You can download a pre-built package of the Rapfi engine and the Yixinboard GUI in the latest release.
This repository contains the following files and several related subprojects:
- Readme.md, the file you are currently reading.
- Copying.txt, a text file containing the GNU General Public License version 3.
- AUTHORS, a text file with the list of authors for the Rapfi project.
- Rapfi, a subdirectory containing the full source code of the Rapfi Gomoku/Renju engine, including a CMakeList.txt that can be used to compile Rapfi with CMake.
- Gomocalc, a subproject containing the source code of the web application Gomoku Calculator.
- Trainer, a subproject containing the source code for the NNUE training code.
- Networks, a submodule containing the latest network weights and config file to be used with the Rapfi engine.
To use Rapfi engine, first acquire the engine executable either by getting it from Github releases or compiling it yourself. After that, acquire the preset config file, as well as both classical and NNUE evaluation weights from the network repo. Place all weight files and config file in the directory containing the Rapfi engine executable, then Rapfi will automatically find and load required files.
When using the Rapfi engine, a user interface program or a match manager program communicates with the engine by sending commands and receiving results via a process pipe. The Piskvork protocol describes a standard text-based protocol used to communicates with a Gomoku/Renju engine, which is the default protocol that Rapfi uses when started with no extra commands. Besides the basic protocol, Rapfi also supports the extra commands from the Yixin-Board extension. In addition, Rapfi supports some custom command extensions which are listed in the documentation.
For more information on the Piskvork protocol, please see the wiki.
You can build Rapfi engine from source in an environment with CMake installed. Rapfi can be compiled with common compilers with C++17 supports such as msvc, gcc and clang. With cmake and compiler installed and available from shell, Rapfi can be compiled with following commands.
cd Rapfi
mkdir build && cd build
cmake .. -DCMAKE_BUILD_TYPE=Release
cmake --build .The default setup builds Rapfi with multi-threading and AVX2 support. To build it for running on older CPU without AVX2 support, AVX2 and AVX usage can be disable through CMake options. To see description for other CMake compile options, please refer to CMakeLists.txt.
cmake .. -DCMAKE_BUILD_TYPE=Release -DUSE_AVX=OFF -DUSE_AVX2=OFFIt is recommended to use the Clang compiler, which provides the best speed across different compilers. When compiling for Windows, consider using one of LLVM/Clang for Windows / Clang-CL for Visual Studio / MinGW-w64-Clang, which compiles the engine binary with significantly higher speed than the builtin MSVC compiler in Visual Studio.
For more detailed instructions for building on all platforms, please refer to the wiki.
Rapfi is free and distributed under the GNU General Public License version 3 (GPL v3). Essentially, this means you are free to do almost exactly what you want with the program, including distributing it among your friends, making it available for download from your website, selling it (either by itself or as part of some bigger software package), or using it as the starting point for a software project of your own.
The only real limitation is that whenever you distribute Rapfi in some way, you MUST always include the license and the full source code (or a pointer to where the source code can be found) to generate the exact binary you are distributing. If you make any changes to the source code, these changes must also be made available under GPL v3.