Skip to main content

memmap-replay-buffer

An easy-to-use numpy memmap replay buffer for RL and other sequence-based learning tasks.

Install

$ pip install memmap-replay-buffer

Usage

Supports trajectory-level, timestep-level, and n-step transition dataloading from a single stored buffer.

import torch
from memmap_replay_buffer import ReplayBuffer

# initialize buffer

buffer = ReplayBuffer(
    './replay_data',
    max_episodes = 1000,
    max_timesteps = 500,
    fields = dict(
        state = ('float', (3, 16, 16), 0.),    # type, shape, and optional default value
        action = ('int', 2),
        reward = 'float'                       # default shape is ()
    ),
    meta_fields = dict(
        task_id = 'int'
    ),
    circular = True,
    overwrite = True
)

# store 4 episodes

for _ in range(4):
    with buffer.one_episode(task_id = 1):
        for _ in range(100):
            buffer.store(
                state = torch.randn(3, 16, 16),
                action = torch.randint(0, 4, (2,)).numpy(),
                reward = 1.0
            )

# rehydrate from disk

buffer_rehydrated = ReplayBuffer.from_folder('./replay_data')
assert buffer_rehydrated.num_episodes == 4

Trajectory-level

Variable-length trajectories, automatically padded with mask and lengths.

dataloader = buffer.dataloader(
    batch_size = 2,
    return_mask = True,
    to_named_tuple = ('state', 'action', 'reward', 'task_id', '_mask', '_lens')
)

for state, action, reward, task_id, mask, lens in dataloader:
    assert state.shape   == (2, 100, 3, 16, 16)
    assert action.shape  == (2, 100, 2)
    assert reward.shape  == (2, 100)
    assert task_id.shape == (2,)

    assert lens.shape    == (2,)
    assert mask.shape    == (2, 100)

Timestep-level

Individual timesteps across episodes, with optional filter_meta for conditioning.

dataloader = buffer.dataloader(
    batch_size = 8,
    filter_meta = dict(
        task_id = 1
    ),
    to_named_tuple = ('state', 'action', 'task_id'),
    timestep_level = True,
    drop_last = True
)

for state, action, task_id in dataloader:
    assert state.shape   == (8, 3, 16, 16)
    assert action.shape  == (8, 2)
    assert task_id.shape == (8,)

N-step transitions

Fetches current_fields at $t$, next_fields at $t + n$ (prefixed next_), and sequence_fields from $t$ to $t + n$ (prefixed seq_, zero-padded at episode boundaries). Use fieldname_map to remap to your model's kwargs.

dataloader = buffer.dataloader(
    batch_size = 4,
    n_steps = 5,
    current_fields = ('state',),
    next_fields = ('state',),
    sequence_fields = ('action', 'reward'),
    to_named_tuple = ('state', 'next_state', 'action_chunk', 'rewards', 'n_step_lens'),
    fieldname_map = {
        'seq_action': 'action_chunk',
        'seq_reward': 'rewards'
    }
)

for state, next_state, action_chunk, rewards, n_step_lens in dataloader:
    assert state.shape == (4, 3, 16, 16)
    assert next_state.shape == (4, 3, 16, 16)
    assert action_chunk.shape == (4, 5, 2)
    assert rewards.shape == (4, 5)
    assert n_step_lens.shape == (4,)

Storing whole episodes

store_episode takes one tensor per field, all sharing the same time dimension (meta fields are scalars or per-episode shapes).

buffer.store_episode(
    state = torch.randn(100, 3, 16, 16),
    action = torch.randint(0, 4, (100, 2)),
    reward = torch.randn(100),
    task_id = 1
)

Batched parallel collection

When collecting from multiple parallel environments, batched_episode + store_batch keeps every environment at the same timestep. create_collector additionally accumulates group-batched data and stores finished episodes for you.

with buffer.batched_episode(batch_size = 4, task_id = [0, 1, 2, 3]):
    for t in range(100):
        buffer.store_batch(
            state = states,     # (4, 3, 16, 16)
            action = actions    # (4, 2)
        )

Updating data in place

update overwrites already-stored episodes, e.g. for bootstrapped returns or value targets.

buffer.update(returns = torch.randn(3, 100))            # all populated episodes
buffer.update(episode_ids, returns = returns_for_ids)   # specific episodes
buffer.update(0, returns = returns_for_one)             # scalar index

Pulling everything at once

all_data = buffer.get_all_data()  # dict of tensors, time-padded to the longest episode

Rendering episodes to video

When a field holds one frame per timestep, save_video renders an episode to .mp4 or .gif (needs pip install memmap-replay-buffer[video]). The image field is auto-detected, and frames may be uint8 or float in [0., 1.]. Pass a list of episodes to concatenate them in time.

buffer.save_video('./episode-0.mp4', episode_index = 0, fps = 30)
buffer.save_video('./episodes-0-3-5.mp4', episode_index = [0, 3, 5], fps = 30)

trajectory_to_video(frames, path, fps) is exported for plain (time, height, width, channels) arrays.

The same is available from the command line, with --sheet for a contact sheet and --serve for a minimal local frontend. --episode and --field accept comma-delimited lists - with multiple cameras (image-like fields), one video is written per field (<name>.<field>.<ext>) and the frontend plays them side by side, synchronized, with a live frame counter to the side. The frontend has frame-level controls: a timeline scrubber, single-frame stepping (buttons, left/right arrows, shift for 10, or mouse wheel over the videos), play/pause, and slowdown playback (down to 0.1x).

$ inspect-replay-buffer ./image_data --episode 0,3,5 --field front,wrist --output replay.mp4 --serve 8000

Reopening, read-only, and clearing

overwrite = False (or from_folder) rehydrates an existing buffer from disk; the stored config is validated against the requested one, so mismatched fields/max_episodes raise a clear error. read_only = True guarantees no files are created or written. clear() wipes all episodes.

buffer = ReplayBuffer.from_folder('./replay_data', read_only = True)
buffer = ReplayBuffer('./replay_data', max_episodes = 1000, max_timesteps = 500, fields = ..., overwrite = False)
buffer.clear()

Concatenating buffers

ConcatReplayBuffer combines several (read-only) buffers of identical fields into one dataset.

from memmap_replay_buffer import ConcatReplayBuffer

concat = ConcatReplayBuffer(['./replay_data_a', './replay_data_b'])
dataloader = concat.dataloader(batch_size = 2, return_mask = True)

Notes

  • circular = True overwrites the oldest episodes once the buffer is full; circular = False raises when full.
  • Fields missing from store are filled with their declared default value (or zeros).
  • flush_every_store_step controls how often the memmaps are flushed to disk while storing (default 1; raise it for faster collection at the cost of durability).
  • ReplayBufferH5PY (pip install h5py) is an HDF5-backed variant with the same interface, optionally gzip-compressed.

Metadata

Release files for memmap-replay-buffer 0.2.3

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

Source distribution (sdist)

Source distribution for memmap-replay-buffer 0.2.3
File Size Uploaded
memmap_replay_buffer-0.2.3.tar.gz 37.7 kB Details

Built distribution (wheel)

Table of built distributions (wheels) for memmap-replay-buffer 0.2.3
File Interpreter ABI Platform
memmap_replay_buffer-0.2.3-py3-none-any.whl Python 3 none any Details

Total release size: 67.5 kB

Release files / memmap_replay_buffer-0.2.3.tar.gz

Download URL memmap_replay_buffer-0.2.3.tar.gz
Size 37.7 kB
Tags Source
SHA-256 checksum
How to use checksums
ceab69640962d2b3f2b7f7c727fbe387a0b32923b2c6ea58cbb7b3ad2a84300f
BLAKE2b-256 checksum
How to use checksums
f375437d3a45ac0909ca865ce7fed7315a7fd401db52c9a2179d4e1b8b25bdb3
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via uv/0.8.17

Release files / memmap_replay_buffer-0.2.3-py3-none-any.whl

Download URL memmap_replay_buffer-0.2.3-py3-none-any.whl
Size 29.8 kB
Tags Python 3
SHA-256 checksum
How to use checksums
27200bd39bd9cdebc94ecec3015802d42f12f6522603271fb41b5dcac56ab79c
BLAKE2b-256 checksum
How to use checksums
adb27092f28743b4133a22e2f309f1f03e6e73606d49fc588669787b48b25f7f
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via uv/0.8.17
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