Skip to main content

A minimal RL library for infinite horizon tasks.

Project description

rlstack: A Minimal RL Library

rlstack is a minimal RL library that can simulate highly parallelized, infinite horizon environments, and can train a PPO policy using those environments, achieving up to 1M environment transitions (and one policy update) per second using a single NVIDIA RTX 2080.

Quick Start

Installation

Install with pip for the latest (stable) version.

pip install rlstack

Install from GitHub for the latest (unstable) version.

git clone https://github.com/theOGognf/rlstack.git
pip install ./rlstack/

Basic Usage

Train a policy with PPO and log training progress with MLflow using the high-level trainer interface (this updates the policy indefinitely).

from rlstack import Trainer
from rlstack.env import DiscreteDummyEnv

trainer = Trainer(DiscreteDummyEnv)
trainer.run()

Collect environment transitions and update a policy directly using the low-level algorithm interface (this updates the policy once).

from rlstack import Algorithm
from rlstack.env import DiscreteDummyEnv

algo = Algorithm(DiscreteDummyEnv)
algo.collect()
algo.step()

The trainer interface is the most popular interface for policy training workflows, whereas the algorithm interface is useful for lower-level customization of policy training workflows.

Concepts

rlstack is minimal in that it limits the number of interfaces required for training a policy with PPO, even for customized policies, without restrictions on observation and action specs, custom models, and custom action distributions.

rlstack is built around six key concepts:

  • The environment: The simulation that the policy learns to interact with. The environment is always user-defined.

  • The model: The policy parameterization that determines how the policy processes environment observations and how parameters for the action distribution are generated. The model is usually user-defined (default models are sometimes sufficient depending on the environment’s observation and action specs).

  • The action distribution: The mechanism for representing actions conditioned on environment observations and model outputs. Environment actions are ultimately sampled from the action distribution. The action distribution is sometimes user-defined (default action distributions are usually sufficient depending on the environment’s observation and action specs).

  • The policy: The union of the model and the action distribution that actually calls and samples from the model and action distribution, respectively. The policy handles some pre/post -processing on its I/O to make it more convenient to sample from the model and action distribution together. The policy is rarely user-defined.

  • The algorithm: The PPO implementation that uses the environment to train the policy (i.e., update the model’s parameters). All hyperparameters and customizations are set with the algorithm. The algorithm is rarely user-defined.

  • The trainer: The high-level interface for using the algorithm to train indefinitely or until some condition is met. The trainer directly integrates with MLflow to track experiments and training progress. The trainer is never user-defined.

Quick Examples

Customizing Training Runs

Use a custom distribution and custom hyperparameters by passing options to the trainer (or algorithm) interface.

from rlstack import SquashedNormal, Trainer
from rlstack.env import ContinuousDummyEnv

trainer = Trainer(
    ContinuousDummyEnv,
    distribution_cls=SquashedNormal,
    gae_lambda=0.99,
    gamma=0.99,
)
trainer.run()

Training a Recurrent Policy

Swap to the recurrent flavor of the trainer (or algorithm) interface to train a recurrent model and policy. The recurrent interfaces use canned and default recurrent models depending on the environment’s observation and action specs.

from rlstack import RecurrentTrainer
from rlstack.env import DiscreteDummyEnv

trainer = RecurrentTrainer(DiscreteDummyEnv)
trainer.run()

Training on a GPU

Specify the device used across the environment, model, and algorithm.

from rlstack import Trainer
from rlstack.env import DiscreteDummyEnv

trainer = Trainer(DiscreteDummyEnv, device="cuda")
trainer.run()

Minimizing GPU Memory Usage

Enable policy updates with gradient accumulation and/or Automatic Mixed Precision (AMP) to minimize GPU memory usage so you can simulate more environments or use larger models.

import torch.optim as optim

from rlstack import Trainer
from rlstack.env import DiscreteDummyEnv

trainer = Trainer(
    DiscreteDummyEnv,
    optimizer_cls=optim.SGD,
    accumulate_grads=True,
    enable_amp=True,
    sgd_minibatch_size=8192,
    device="cuda",
)
trainer.run()

Specifying Training Stop Conditions

Specify training stop conditions based on training statistics to stop training early when statistics plateau, hit a limit, stop increasing or decreasing, etc..

from rlstack import Trainer
from rlstack.conditions import Plateaus
from rlstack.env import DiscreteDummyEnv

trainer = Trainer(DiscreteDummyEnv)
trainer.run(stop_conditions=[Plateaus("returns/mean", rtol=0.05)])

Why rlstack?

TL;DR: rlstack focuses on a niche subset of RL that simplifies the overall library while allowing fast and fully customizable environments, models, and action distributions.

There are many high quality, open-sourced RL libraries. Most of them take on the daunting task of being a monolithic, one-stop-shop for everything RL, attempting to support as many algorithms, environments, models, and compute capabilities as possible. Naturely, this monolothic goal has some drawbacks:

  • The software becomes more dense with each supported feature, making the library all-the-more difficult to customize for a specific use case.

  • The software becomes less performant for a specific use case. RL practitioners typically end up accepting the cost of transitioning to expensive and difficult-to-manage compute clusters to get results faster.

There’s a handful of high quality, open-sourced RL libraries that tradeoff feature richness to reduce these drawbacks. However, each library still doesn’t provide enough speed benefit to warrant the switch from a monolithic repo, or is still too complex to adapt to a specific use case.

rlstack is a niche RL library that finds a goldilocks zone between the feature support and speed/complexity tradeoff by making some key assumptions:

  • Environments are highly parallelized and their parallelization is entirely managed within the environment. This allows rlstack to ignore distributed computing design considerations.

  • Environments are infinite horizon (i.e., they have no terminal conditions). This allows rlstack to reset environments at the same, fixed horizon intervals, greatly simplifying environment and algorithm implementations.

  • The only supported ML framework is PyTorch and the only supported algorithm is PPO. This allows rlstack to ignore layers upon layers of abstraction, greatly simplifying the overall library implementation.

The end result is a minimal and high throughput library that can train policies to solve complex tasks on a single NVIDIA RTX 2080 within minutes.

Unfortunately, this means rlstack doesn’t support as many use cases as a monolithic RL library might. In fact, rlstack is probably a bad fit for your use case if:

  • Your environment isn’t parallelizable.

  • Your environment must contain terminal conditions and can’t be reformulated as an infinite horizon task.

  • You want to use an ML framework that isn’t PyTorch or you want to use an algorithm that isn’t a variant of PPO.

However, if rlstack does fit your use case, it can do wonders for your RL workflow.

Project details


Download files

Download the file for your platform. If you're not sure which to choose, learn more about installing packages.

Source Distribution

rlstack-1.1.0.tar.gz (84.3 kB view hashes)

Uploaded Source

Built Distribution

rlstack-1.1.0-py3-none-any.whl (90.2 kB view hashes)

Uploaded Python 3

Supported by

AWS AWS Cloud computing and Security Sponsor Datadog Datadog Monitoring Fastly Fastly CDN Google Google Download Analytics Microsoft Microsoft PSF Sponsor Pingdom Pingdom Monitoring Sentry Sentry Error logging StatusPage StatusPage Status page