Volatile

KO | EN

gitlite — search

#tailwindcss #pytorch #hacktoberfest #nodejs #vue #cloud-native #containers #computer-vision #kotlin #css

(★ 9)

Volatile is a UCI compatible C++ based chess engine which supports both HCE and NNUE.

파일 탐색기

ZIP 다운로드

- AGENTS.md
- ARCHITECTURE.md
- CONTRIBUTION_SCOPE.md
- - Bitboard.hpp
  - Board.hpp
  - ConstantArrays.hpp
  - Constants.hpp
  - Logo.hpp
  - Move.hpp
  - MoveGen.hpp
- - Datagen.hpp
  - OpeningBook.hpp
  - PawnTable.hpp
  - Search.hpp
  - Tablebase.hpp
  - TimeManager.hpp
  - TT.hpp
- - UCIHandler.hpp
- common.h
- checknnue.py
- converter.py
- LogoGenerator.py
- - Bitboard.cpp
  - Board.cpp
  - BoardMove.cpp
  - BoardUtils.cpp
  - CMakeLists.txt
  - ConstantArrays.cpp
  - Move.cpp
  - MoveGen.cpp
- - CMakeLists.txt
- - CMakeLists.txt
  - tbconfig.h
  - tbcore.c
  - tbcore.h
  - tbprobe.c
  - tbprobe.h
- - CMakeLists.txt
  - Datagen.cpp
  - MoveOrdering.cpp
  - OpeningBook.cpp
  - Quiescence.cpp
  - Search.cpp
  - Tablebase.cpp
  - TT.cpp
- - CMakeLists.txt
  - UCIHandler.cpp
- CMakeLists.txt
- main.cpp
- check_integrity.bat
- check_integrity.sh
- checksum.md5
- fsum.exe
- KBBBvK.rtbw
- KBBBvK.rtbz
- KBBNvK.rtbw
- KBBNvK.rtbz
- KBBPvK.rtbw
- KBBPvK.rtbz
- KBBvK.rtbw
- KBBvK.rtbz
- KBBvKB.rtbw
- KBBvKB.rtbz
- KBBvKN.rtbw
- KBBvKN.rtbz
- KBBvKP.rtbw
- KBBvKP.rtbz
- KBBvKQ.rtbw
- KBBvKQ.rtbz
- KBBvKR.rtbw
- KBBvKR.rtbz
- KBNNvK.rtbw
- KBNNvK.rtbz
- KBNPvK.rtbw
- KBNPvK.rtbz
- KBNvK.rtbw
- KBNvK.rtbz
- KBNvKB.rtbw
- KBNvKB.rtbz
- KBNvKN.rtbw
- KBNvKN.rtbz
- KBNvKP.rtbw
- KBNvKP.rtbz
- KBNvKQ.rtbw
- KBNvKQ.rtbz
- KBNvKR.rtbw
- KBNvKR.rtbz
- KBPPvK.rtbw
- KBPPvK.rtbz
- KBPvK.rtbw
- KBPvK.rtbz
- KBPvKB.rtbw
- KBPvKB.rtbz
- KBPvKN.rtbw
- KBPvKN.rtbz
- KBPvKP.rtbw
- KBPvKP.rtbz
- KBPvKQ.rtbw
- KBPvKQ.rtbz
- KBPvKR.rtbw
- KBPvKR.rtbz
- KBvK.rtbw
- KBvK.rtbz
- KBvKB.rtbw
- KBvKB.rtbz
- KBvKN.rtbw
- KBvKN.rtbz
- KBvKP.rtbw
- KBvKP.rtbz
- KNNNvK.rtbw
- KNNNvK.rtbz
- KNNPvK.rtbw
- KNNPvK.rtbz
- KNNvK.rtbw
- KNNvK.rtbz
- KNNvKB.rtbw
- KNNvKB.rtbz
- KNNvKN.rtbw
- KNNvKN.rtbz
- KNNvKP.rtbw
- KNNvKP.rtbz
- KNNvKQ.rtbw
- KNNvKQ.rtbz
- KNNvKR.rtbw
- KNNvKR.rtbz
- KNPPvK.rtbw
- KNPPvK.rtbz
- KNPvK.rtbw
- KNPvK.rtbz
- KNPvKB.rtbw
- KNPvKB.rtbz
- KNPvKN.rtbw
- KNPvKN.rtbz
- KNPvKP.rtbw
- KNPvKP.rtbz
- KNPvKQ.rtbw
- KNPvKQ.rtbz
- KNPvKR.rtbw
- KNPvKR.rtbz
- KNvK.rtbw
- KNvK.rtbz
- KNvKN.rtbw
- KNvKN.rtbz
- KNvKP.rtbw
- KNvKP.rtbz
- KPPPvK.rtbw
- KPPPvK.rtbz
- KPPvK.rtbw
- KPPvK.rtbz
- KPPvKB.rtbw
- KPPvKB.rtbz
- KPPvKN.rtbw
- KPPvKN.rtbz
- KPPvKP.rtbw
- KPPvKP.rtbz
- KPPvKQ.rtbw
- KPPvKQ.rtbz
- KPPvKR.rtbw
- KPPvKR.rtbz
- KPvK.rtbw
- KPvK.rtbz
- KPvKP.rtbw
- KPvKP.rtbz
- KQBBvK.rtbw
- KQBBvK.rtbz
- KQBNvK.rtbw
- KQBNvK.rtbz
- KQBPvK.rtbw
- KQBPvK.rtbz
- KQBvK.rtbw
- KQBvK.rtbz
- KQBvKB.rtbw
- KQBvKB.rtbz
- KQBvKN.rtbw
- KQBvKN.rtbz
- KQBvKP.rtbw
- KQBvKP.rtbz
- KQBvKQ.rtbw
- KQBvKQ.rtbz
- KQBvKR.rtbw
- KQBvKR.rtbz
- KQNNvK.rtbw
- KQNNvK.rtbz
- KQNPvK.rtbw
- KQNPvK.rtbz
- KQNvK.rtbw
- KQNvK.rtbz
- KQNvKB.rtbw
- KQNvKB.rtbz
- KQNvKN.rtbw
- KQNvKN.rtbz
- KQNvKP.rtbw
- KQNvKP.rtbz
- KQNvKQ.rtbw
- KQNvKQ.rtbz
- KQNvKR.rtbw
- KQNvKR.rtbz
- KQPPvK.rtbw
- KQPPvK.rtbz
- KQPvK.rtbw
- KQPvK.rtbz
- KQPvKB.rtbw
- KQPvKB.rtbz
- KQPvKN.rtbw
- KQPvKN.rtbz
- KQPvKP.rtbw
- KQPvKP.rtbz
- KQPvKQ.rtbw
- KQPvKQ.rtbz
- KQPvKR.rtbw
- KQPvKR.rtbz
- KQQBvK.rtbw
- KQQBvK.rtbz
- KQQNvK.rtbw
- KQQNvK.rtbz
- KQQPvK.rtbw
- KQQPvK.rtbz
- KQQQvK.rtbw
- KQQQvK.rtbz
- KQQRvK.rtbw
- KQQRvK.rtbz
- KQQvK.rtbw
- KQQvK.rtbz
- KQQvKB.rtbw
- KQQvKB.rtbz
- KQQvKN.rtbw
- KQQvKN.rtbz
- KQQvKP.rtbw
- KQQvKP.rtbz
- KQQvKQ.rtbw
- KQQvKQ.rtbz
- KQQvKR.rtbw
- KQQvKR.rtbz
- KQRBvK.rtbw
- KQRBvK.rtbz
- KQRNvK.rtbw
- KQRNvK.rtbz
- KQRPvK.rtbw
- KQRPvK.rtbz
- KQRRvK.rtbw
- KQRRvK.rtbz
- KQRvK.rtbw
- KQRvK.rtbz
- KQRvKB.rtbw
- KQRvKB.rtbz
- KQRvKN.rtbw
- KQRvKN.rtbz
- KQRvKP.rtbw
- KQRvKP.rtbz
- KQRvKQ.rtbw
- KQRvKQ.rtbz
- KQRvKR.rtbw
- KQRvKR.rtbz
- KQvK.rtbw
- KQvK.rtbz
- KQvKB.rtbw
- KQvKB.rtbz
- KQvKN.rtbw
- KQvKN.rtbz
- KQvKP.rtbw
- KQvKP.rtbz
- KQvKQ.rtbw
- KQvKQ.rtbz
- KQvKR.rtbw
- KQvKR.rtbz
- KRBBvK.rtbw
- KRBBvK.rtbz
- KRBNvK.rtbw
- KRBNvK.rtbz
- KRBPvK.rtbw
- KRBPvK.rtbz
- KRBvK.rtbw
- KRBvK.rtbz
- KRBvKB.rtbw
- KRBvKB.rtbz
- KRBvKN.rtbw
- KRBvKN.rtbz
- KRBvKP.rtbw
- KRBvKP.rtbz
- KRBvKQ.rtbw
- KRBvKQ.rtbz
- KRBvKR.rtbw
- KRBvKR.rtbz
- KRNNvK.rtbw
- KRNNvK.rtbz
- KRNPvK.rtbw
- KRNPvK.rtbz
- KRNvK.rtbw
- KRNvK.rtbz
- KRNvKB.rtbw
- KRNvKB.rtbz
- KRNvKN.rtbw
- KRNvKN.rtbz
- KRNvKP.rtbw
- KRNvKP.rtbz
- KRNvKQ.rtbw
- KRNvKQ.rtbz
- KRNvKR.rtbw
- KRNvKR.rtbz
- KRPPvK.rtbw
- KRPPvK.rtbz
- KRPvK.rtbw
- KRPvK.rtbz
- KRPvKB.rtbw
- KRPvKB.rtbz
- KRPvKN.rtbw
- KRPvKN.rtbz
- KRPvKP.rtbw
- KRPvKP.rtbz
- KRPvKQ.rtbw
- KRPvKQ.rtbz
- KRPvKR.rtbw
- KRPvKR.rtbz
- KRRBvK.rtbw
- KRRBvK.rtbz
- KRRNvK.rtbw
- KRRNvK.rtbz
- KRRPvK.rtbw
- KRRPvK.rtbz
- KRRRvK.rtbw
- KRRRvK.rtbz
- KRRvK.rtbw
- KRRvK.rtbz
- KRRvKB.rtbw
- KRRvKB.rtbz
- KRRvKN.rtbw
- KRRvKN.rtbz
- KRRvKP.rtbw
- KRRvKP.rtbz
- KRRvKQ.rtbw
- KRRvKQ.rtbz
- KRRvKR.rtbw
- KRRvKR.rtbz
- KRvK.rtbw
- KRvK.rtbz
- KRvKB.rtbw
- KRvKB.rtbz
- KRvKN.rtbw
- KRvKN.rtbz
- KRvKP.rtbw
- KRvKP.rtbz
- KRvKR.rtbw
- KRvKR.rtbz
- CMakeLists.txt
- RunAllTests.cpp
- RunEval.cpp
- RunMoveGen.cpp
- RunSPRT.cpp
- - UHO_Lichess_4852_v1.epd.part_aa
  - UHO_Lichess_4852_v1.epd.part_ab
- - GamePairs_rescoring_tool.7z
  - RawData.zip
  - ReadMe.txt
  - Testresults.zip
.gitignore
CMakeLists.txt
CMakePresets.json
README.md
requirements-sys.txt
requirements.txt
setup.bat
setup.sh
VCE_logo.png

# CDN으로 사용하기

jsDelivr

jsDelivr는 공개 GitHub 리포지토리를 별도 설정 없이 CDN으로 즉시 서빙합니다. 버전과 파일을 고르면 웹페이지에 바로 붙일 수 있는 링크와 예시 코드가 만들어집니다.

버전

파일

링크

예시

// repository documentation

Was this content helpful?

★ 0 (0 ratings)

Welcome to **Volatile**! This is a UCI-compatible chess engine written in C++ with a strong focus on modularity and performance.

### A Little Backstory...
I've always dreamed of creating a chess engine from scratch that might, just *maybe*, beat Stockfish one day! We aren't quite there yet, but currently, Volatile is playing at a strong **2200-2400 Elo** level and can sometimes draw or even win against Stockfish level 7 on Lichess. You can actually watch or challenge the bot on Lichess here: [**@I_am_Human_Trust**](https://lichess.org/@/I_am_Human_Trust).

I'm not a professional chess engine developer, so I might be unaware of some of the deeply ingrained "best practices" of the field. However, I am trying to learn as much as possible along the way and apply those lessons here. This is a very active repository with *huge* scope for improvement. I am always looking for direction, and **every single idea or optimization you bring to the table is welcomed with open arms!**

### Welcome Newcomers! 🌱
If you are a newcomer looking to contribute to a solid C/C++ repository, you are incredibly welcome here! This repository is a fantastic learning ground. Because we are still in the very early stages of development, it's really easy to contribute, get your hands dirty, and get a real sense of satisfaction while learning alongside us.
## Current Architecture & Features

Volatile currently uses a unified, highly optimized Alpha-Beta search backend that powers two distinct evaluation paradigms, toggleable via CMake.

**Evaluation Backends:**
- **HCE (Hand-Crafted Evaluation):** The default (`USE_NNUE=OFF`), classic evaluation based on piece-square tables, phased material, mobility, and pawn structures.
- **NNUE (Efficiently Updatable Neural Networks):** The modern (`USE_NNUE=ON`), highly advanced neural network evaluator. *Status: Currently in active development (accumulator SIMD implementations and training data generation ongoing).*

**Search Algorithm (Unified for both HCE and NNUE):**
- Principal Variation Search (PVS) / Negamax framework.
- Iterative Deepening with Aspiration Windows.
- Quiescence Search with Delta Pruning.
- Transposition Table (TT) with lockless hashing.

**Pruning & Reductions:**
- Null Move Pruning (NMP).
- Late Move Reductions (LMR).
- Reverse Futility Pruning (RFP) / Static Null Move Pruning.
- ProbCut and Singular Extensions.

**Move Ordering:**
- Hash moves from TT.
- Static Exchange Evaluation (SEE) for capture ordering and pruning.
- Killer Move Heuristic.
- History Heuristics (including Correction Histories for both pawns and non-pawns).

**Other Features:**
- **Syzygy Tablebases:** Integrated via Fathom for perfect endgame play.
- **Opening Book:** Support for Polyglot `.bin` opening books.
- **Data Generation:** Built-in tools to generate self-play data (`datagen` command).
- **Tuning:** Built-in SPSA tuning support (`tune` command).

## Documentation Overview

To keep the repository clean and organized, detailed information is logically grouped into specific markdown files within the `docs/` directory.

**🤖 AI Agents: You MUST read `docs/AGENTS.md` properly at least once before beginning any work on this repository.**

- **[`docs/AGENTS.md`](docs/AGENTS.md):** The central hub for AI agents. It contains high-level overviews, refactoring rules, and directory structures.
- **[`docs/ARCHITECTURE.md`](docs/ARCHITECTURE.md):** A detailed deep-dive into the engine's modular architecture, specifically explaining the zero-overhead implementation split between HCE and NNUE, and how the unified Alpha-Beta search flawlessly handles both.
- **[`docs/CONTRIBUTION_SCOPE.md`](docs/CONTRIBUTION_SCOPE.md):** A detailed list of all undone, incomplete, and work-in-progress tasks (such as NNUE SIMD inference and the Test Suite). Newcomers should look here for ideas on what to work on!

## Contribution Guidelines (For Users and AI Agents)

We welcome contributions of all sizes! To maintain a high-quality, maintainable, and high-performance codebase, all contributors (both human and AI) must adhere to the following rules:

1. **Proper Abstraction & SOLID Principles:** Everything must be properly abstracted. Leverage SOLID design patterns. In C++, prefer stack allocation and RAII over manual memory management to guarantee exception safety and clear resource ownership.
2. **File Size Limits:** No file should exceed 700 lines of code. If a file grows larger, refactor and split it into smaller, focused modules to keep the code clean and maintainable, unless splitting is strictly unwanted due to architecture.
3. **Extend AI Capabilities:** You can choose to add new skills in the `.agent/` directory that you think AI agents will find useful for future workflows.
4. **Single Commit Policy:** All changes for a particular task must ultimately be in one commit. Splitting into multiple commits during development is fine, but you must squash them into a single, cohesive commit after review and before merging.
5. **Discuss Before Implementing:** Always propose what you wish to improve via a discussion or issue first. This ensures no one else is already working on it and aligns with the project's goals.
6. **Zero Flaw Tolerance:** Your contribution, no matter how small, is always welcomed, but it must be flawless.
7. **Dual Build Verification:** Because Volatile supports both Hand-Crafted Evaluation (HCE) and NNUE backends, you must build and test your changes with both `USE_NNUE=OFF` and `USE_NNUE=ON` to ensure no build configuration is broken.

## Prerequisites

To build and run Volatile, you will need a modern C++ compiler (supporting C++17), CMake, and Python 3 (for auxiliary scripts). Below are the commands to install the required system packages across different operating systems.

### Setting Up Python Dependencies

Volatile includes a few Python scripts for data processing and utility generation. It is recommended to use a virtual environment (`venv`) to avoid interfering with system-wide Python packages.

We provide a cross-platform setup script that automates this:

1. **Linux / macOS:** Run `./setup.sh`
2. **Windows:** Run `setup.bat`

> [!NOTE]
> The Python virtual environment is **strictly optional** for building and running the core C++ chess engine itself. You only need it if you plan to use the Python utility scripts. You can activate the venv by `source .venv/bin/activate` on Linux/ MacOS or `.venv\Scripts\activate` on Windows. 
>
> **Dependency Resolution:**
> We split our dependencies into two files for cross-platform stability (especially on constrained environments like Android/Termux):
> - `requirements-sys.txt`: Contains heavy C-extension packages (like `numpy` and `Pillow`). On constrained systems, the setup script installs these natively via system package managers (e.g., `pkg`) to avoid source compilations.
> - `requirements.txt`: Contains pure Python packages (like `chess`). 
> 
> *Note: The setup scripts will automatically feed both files to pip on standard platforms, but will strictly isolate them on Termux to prevent catastrophic source compilation failures.*

## Building Volatile

Volatile is built using CMake.

**To build the default HCE engine:**
```bash
mkdir build
cd build
cmake .. -DUSE_NNUE=OFF
make -j$(nproc)
```
Or

**To build the NNUE engine:**

```bash
cmake .. -DUSE_NNUE=ON
make -j$(nproc)
```
**To run the engine:**
```bash
./Volatile
```
(You can then interact with the engine using the standard UCI protocol.)

## Testing Framework
Any change to search or evaluation logic **must** be validated via SPRT testing. We use a custom C++ test runner suite that wraps `fastchess` or `cutechess`.

### The Standard Contribution Workflow
If you are tweaking the search algorithms, here is the exact step-by-step workflow you should follow to prove your changes work:

1. **The Baseline:** Compile the unmodified engine (exactly as it is on the `main` branch) inside a folder named `build_base/`.
2. **The Modification:** Get your hands dirty! Edit the code in `src/` to add your awesome new search optimization.
3. **The Test Engine:** Compile your new changes in the standard `build/` folder.
4. **Configuration (Optional):** Open `tests/RunSPRT.cpp` and update the `runnerPath` if you have `fastchess` or `cutechess` installed in a custom location.
5. **The Test Build:** Create a dedicated folder for testing (which will automatically detect it should build the tests):
   ```bash
   mkdir build_tests && cd build_tests
   cmake ..
   make -j$(nproc)
   ```
6. **The Match:** From inside the `build_tests/` folder, start the SPRT match:
   ```bash
   ./run_sprt
   ```

The C++ code will automatically point to `../build_base/Volatile` and `../build/Volatile`, run the match, and print the live Elo statistics to your screen. If the SPRT passes, you are safe to commit and push your changes! 🎉

> [!IMPORTANT]
> **Mandatory Commit Formatting:** Any SPRT testing output (the exact block printed when the hypothesis is accepted) **must** be strictly pasted into the commit message, right after the sign-off. This rule must be followed for any change or fix touching critical portions of the engine (e.g., search or evaluation).

> [!NOTE]
> For SPRT tests, you **must** have either `fastchess` or `cutechess` installed.
> You can toggle which one is used by changing the `useFastChess` boolean variable inside `tests/RunSPRT.cpp` and set the path to the respective tool by changing the `runnerPath`.

Volatile

파일 탐색기

# CDN으로 사용하기

Was this content helpful?

Recent Feedback

Download README