Skip to main content

MCTS

This package provides a simple way of using Monte Carlo Tree Search in any perfect information domain.

It was originally authored by pbsinclair42. This fork however complies with the Python Naming Convention, provides base classes for implementing states and actions, and includes more comprehensive examples.

Installation

With pip: pip install monte-carlo-tree-search

Without pip: Download the zip/tar.gz file of the latest release, extract it, and run python setup.py install

Quick Usage

In order to run MCTS, you must implement your own State class that extends mcts.base.base.BaseState which can fully describe the state of the world. It must implement four methods:

  • get_current_player(): Returns 1 if it is the maximizer player's turn to choose an action, or -1 for the minimiser player
  • get_possible_actions(): Returns an iterable of all actions which can be taken from this state
  • take_action(action): Returns the state which results from taking action action
  • is_terminal(): Returns True if this state is a terminal state
  • get_reward(): Returns the reward for this state. Only needed for terminal states.

You must also choose a hashable representation for an action as used in get_possible_actions and take_action. Typically, this would be a class with a custom __hash__ method, but it could also simply be a tuple, a string, etc. A BaseAction class is provided for this purpose.

Once these have been implemented, running MCTS is as simple as initializing your starting state, then running:

from mcts.base.base import BaseState
from mcts.searcher.mcts import MCTS


class MyState(BaseState):
    def get_possible_actions(self) -> [any]:
        pass

    def take_action(self, action: any) -> 'BaseState':
        pass

    def is_terminal(self) -> bool:
        pass

    def get_reward(self) -> float:
        pass

    def get_current_player(self) -> int:
        pass


initial_state = MyState()

searcher = MCTS(time_limit=1000)
bestAction = searcher.search(initial_state=initial_state)

Here the unit of time_limit=1000 is milliseconds. You can also use for example iteration_limit=100 to specify the number of rollouts. Exactly one of time_limit and iteration_limit should be specified.

best_action = searcher.search(initial_state=initial_state)
print(best_action)  # the best action to take found within the time limit

To also receive the best reward as a return value set need_details to True in searcher.search(...).

best_action, reward = searcher.search(initial_state=initial_state, need_details=True)
print(best_action)  # the best action to take found within the time limit
print(reward)  # the expected reward for the best action

Parallel processing

For faster rollouts you can run multiple worker processes using search_parallel. Simply provide the desired number of jobs:

best_action = searcher.search_parallel(initial_state=initial_state, n_jobs=4)

Examples

You can find some examples using the MCTS here:

Collaborating

Feel free to raise a new issue for any new feature or bug you've spotted. Pull requests are also welcomed if you're interested in directly improving the project.

Getting Started

  1. Create a virtual environment: python -m venv .venv
  2. Activate the environment and install dependencies: pip install -r requirements.txt
  3. Install the package in editable mode to work on it locally: pip install -e .
  4. Run tests with pytest before submitting a pull request.

Coding Guidelines

Commit message should follow the Conventional Commits specification. This makes contributions easily comprehensible and enables us to automatically generate release notes.

Recommended tooling for developers:

Example commit message

fix: prevent racing of requests

Introduce a request id and a reference to latest request. Dismiss
incoming responses other than from latest request.

Remove timeouts which were used to mitigate the racing issue but are
obsolete now.

Reviewed-by: Z
Refs: #123

Metadata

Release files for monte-carlo-tree-search 2.1.0

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Built distribution (wheel)

Table of built distributions (wheels) for monte-carlo-tree-search 2.1.0
File Interpreter ABI Platform Actions
monte_carlo_tree_search-2.1.0-py3-none-any.whl Python 3 none any Details for monte_carlo_tree_search-2.1.0-py3-none-any.whl

Release files / monte_carlo_tree_search-2.1.0-py3-none-any.whl

Download URL monte_carlo_tree_search-2.1.0-py3-none-any.whl
Size 12.6 kB
Tags Python 3
SHA-256 checksum
How to use checksums
128d4cdf6ebb7617f6029cd54a41ad83b4ff69ab233fb4ad6dec56c8c770274b
BLAKE2b-256 checksum
How to use checksums
ed444530e5dff24bba5d5220ca7d608de80b97effd21c05b29ad12dccde870d3
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via twine/6.1.0 CPython/3.13.5

Security for monte-carlo-tree-search 2.1.0

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

No provenance found

None of the files in this release were uploaded with provenance metadata.

A note on package security

PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.

To learn more about protecting yourself from malicious actors, visit our package security documentation.

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page