Skip to main content

A concurrent wrapper for OpenAI Gym library that runs multiple environments concurrently.

Project description

agymc

gym

For reinforcement learning and concurrency lovers out there ...

TL;DR

  • Mostly the same API as gym, except now multiple environments are run.
  • Envs are run concurrently, which means speedup with time consuming operations such as backprop, render etc..

Intro

This is a concurrent wrapper for OpenAI Gym library that runs multiple environments concurrently, which means running faster in training* without consuming more CPU power.

What exactly is concurrency ?

Maybe you have heard of parallel computing ? When we say we execute things in parallel, we run the program on multiple processors, which offers significant speedup. Concurrency computing has a broader meaning, though. The definition of a concurrent program, is that it is designed not to execute sequentially, and will one day be executed parallelly**. A concurrent program can run on a sigle processor or multiple processors. These tasks may communicate with each other, but have separate private states hidden from others.

Why do we need concurrency on a single processor ?

Some tasks, by nature, takes a lot of time to complete. Downloading a file, for example. Without concurrency, the processor would have to wait for the task to complete before starting to execute the next task. However, with concurrency we could temporarily suspend the current task, and come back later when the task finishes. Without using extra computing power.

So much for introducing concurrency... now, what is gym ?

OpenAI gym, is a Python library that helps research reinforcement learning. Reinforcement learning is a branch from control theory, and focusing mainly on agents interacting with environments. And OpenAI gym provides numerous environments for people to benchmark their beloved reinforcement learning algorithms. For you agents to train in a gym, they say.

Um, so why do we need agymc, do you say ?

Despite its merits, OpenAI gym has one major drawback. It is designed to run one agent on a processor at a time, only. What if you want to run multiple environments on the same processor at a time? Well, it will run, sequentially. Which means slow if you want to train a robot in batches.

Experiments

Using env.render as our bottlenecking operation, runing 200 environments, our versionagymc completes 50 episodes in 4 minutes, while naive gym version takes around twice as long. This is what the madness looks like:

Screenshot_1

Wow, how to use agymc ?

agymc, which combines the power of Python async API and OpenAI gym, hence the name, designed for users to make final Except now the returns are in batches (lists). And except serveral environments are run asynchronously.

Example Usage Code Snippet

import argparse

import agymc

if __name__ == "__main__":
    parser = argparse.ArgumentParser()
    parser.add_argument("--num-envs", type=int)
    parser.add_argument("--episodes", type=int)
    parser.add_argument("--render", action="store_true")
    parser.add_argument("--verbose", action="store_true")
    flags = parser.parse_args()

    num_envs = flags.num_envs
    num_episodes = flags.episodes
    render = flags.render
    verbose = flags.verbose

    envs = agync.make("CartPole-v0", num_envs)
    if verbose:
        import tqdm

        iterable = tqdm.tqdm(range(num_episodes))
    else:
        iterable = range(num_episodes)

    for _ in iterable:
        done = list(False for _ in range(num_envs))
        envs.reset()

        while not all(done):
            if render:
                envs.render()
            action = envs.action_space.sample()
            (_, _, done, _) = envs.step(action)
    envs.close()

* When doing pure gym operation such as sampling, stepping, this library runs slower since this is a wrapper for gym. However, for actions that takes a while to execute, such as backprop and update, sending data back and forth, or even rendering, concurrency makes the operations execute much faster than a naive gym implementation

** If you would like to learn more about concurrency patterns, this video is really informative.

Project details


Download files

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

Files for agymc, version 0.1.1.dev0
Filename, size File type Python version Upload date Hashes
Filename, size agymc-0.1.1.dev0-py3-none-any.whl (7.7 kB) File type Wheel Python version py3 Upload date Hashes View
Filename, size agymc-0.1.1.dev0.tar.gz (5.4 kB) File type Source Python version None Upload date Hashes View

Supported by

Pingdom Pingdom Monitoring Google Google Object Storage and Download Analytics Sentry Sentry Error logging AWS AWS Cloud computing DataDog DataDog Monitoring Fastly Fastly CDN DigiCert DigiCert EV certificate StatusPage StatusPage Status page