POPGym Arcade
POPGym Arcade is a GPU-accelerated Atari-style benchmark and suite of analysis tools for reinforcement learning.
For more details, check out the project website.
Check the documentation for the guide you need — quick start, memory introspection, or reproducing experiments.
Tasks
POPGym Arcade contains pixel-based tasks in the style of the Arcade Learning Environment.
Each environment provides:
- Three difficulty settings
- One observation and action space shared across all envs
- Fully observable and partially observable configurations
- Fast and easy GPU vectorization using
jax - Standardized returns in
[0,1]or[-1, 1]
Baselines
We provide a single training script for all algorithms and memory models. The memax library provides 18 different memory models for use in our script.
RL Algorithms
Getting Started
To install the environments, run
pip install popgym-arcade
If you plan to use our training scripts, install the baselines as well. If you want to play the games yourself, also use the human flag.
pip install 'popgym-arcade[baselines,human]'
[!NOTE] If you do not already have
jaxinstalled, we install CPUjaxby default. For GPU acceleration, runpip install jax[cuda12]after installingpopgym-arcade.
Human Play
The play script installed with pip install popgym-arcade[human] lets you play the games yourself using the arrow keys and spacebar.
popgym-arcade-play NoisyCartPoleEasy # play MDP 256 pixel version
popgym-arcade-play BattleShipEasy -p -o 128 # play POMDP 128 pixel version
Other Useful Libraries
stable-gymnax- A (stable)jax-capablegymnasiumAPImemax- Recurrent models forjaxpopgym- The original collection of POMDPs, implemented innumpypopjaxrl- Ajaxversion ofpopgympopjym- A more readable version ofpopjaxrlenvironments that served as a basis for our work
Citation
If you use POPGym Arcade in your work, please cite it as follows:
@article{wang2025investigating,
title={Investigating Memory in Model-Free RL with POPGym Arcade},
author={Wang, Zekang and He, Zhe and Zhang, Borong and Toledo, Edan and Morad, Steven},
journal={arXiv preprint arXiv:2503.01450},
year={2025}
}
Metadata
Release files for popgym-arcade 0.0.7
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| popgym_arcade-0.0.7.tar.gz | 113.9 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| popgym_arcade-0.0.7-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 265.3 kB
Release files / popgym_arcade-0.0.7.tar.gz
| Download URL | popgym_arcade-0.0.7.tar.gz |
|---|---|
| Size | 113.9 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
db9dc2247872a7100d0e03acb5280c1c04626dcc006c5533d981b8db2e61b5a0
|
|
BLAKE2b-256 checksum How to use checksums |
88aa50908249f19d49a3ad1c0e8bc4f8b65ecb1fe0fe4ddea4f1b1d8812a117a
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Jun 5, 2026.
Transparency logRelease files / popgym_arcade-0.0.7-py3-none-any.whl
| Download URL | popgym_arcade-0.0.7-py3-none-any.whl |
|---|---|
| Size | 151.4 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
9396987c1a6ddfb27cfd37b1fac06350b955c7e715a9bfec2921d19edf0c31d8
|
|
BLAKE2b-256 checksum How to use checksums |
6198d3d8e4c31a8a999452de70e9215b92cd4e7e07267eb5de198f1598a285ea
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Jun 5, 2026.
Transparency log