MO-Playground: Massively Parallelized Multi-Objective Reinforcement Learning for Robotics
Neil Janwani, Ellen Novoseller, Vernon Lawhern, Maegan Tucker,
https://arxiv.org/abs/2603.09237v1
MO-Playground is a collection of multi-objective environments built in JAX for GPU-Accelerated multi-objective RL.
Note that due to double-blind requirements, moplayground's documentation page and pip-installable package is not yet available.
Prerequisites
The code was tested with:
- Ubuntu 22.04
- Python 3.12.12
- CUDA 13.0 (if you want to train policies. Evaluation can happen without a GPU).
Installation
Using the provided ymls, create a new conda environment. If you want to enable GPU based training, run
conda env create -f environment.yml
conda activate moplayground
if you just want to evaluate policies and explore the code (i.e. running on a Mac)
conda env create -f mac_environment.yml
conda activate moplayground
Finally, go to the project root and run
pip3 install -e .
to install the moplayground package.
Evaluation
Create an account at Weights and Biases. Note that the process should be free and you'll be required to paste your API key to get things to work. Educational accounts receive some amount of free storage by the way, which can be useful if you're a student!
Finally, pick an environment from the below list
cheetahhopperwalkeranthumanoidbruce
and download your desired policy.
python3 -m scripts.download_model --env cheetah
note that you can supply a desired save directory via --save_dir.
The default directory is simply results/wandb-downloads.
Finally, you can run the policy via
python3 -m scripts.rollout config_path
where config_path is the config.yaml file where your model was saved.
It will be at save_dir/env_name/config.yaml, where save_dir and env_name are defined above.
Training
To train a pre-existing environment, check out the configuration files in config/.
These files specify everything from model architecture and MORLAX parameters to reward and environment constants.
Choose the config file you want, edit the parameters to your liking, and run
python3 -m scripts.train config_path
where config_path is the path to the config of your choice.
If you downloaded a policy in the past, you can also use those configs to run an identical training run on your system.
Creating your own environment
To create a custom environment, check out how the cheetah environment works at src/moplayground/envs/dmcontrol/cheetah.py.
You should need to make your child class a member of the MultiObjectiveBase class. You will also need to make a config.yaml
file for your environment to specify the training parameters.
Note that support for custom dynamics (i.e. non-mujoco) is coming soon.
Classic Environments
| Environment | Reward 1 | Reward 2 |
|---|---|---|
BRUCE Robotics Example
MO-Playground is demonstrated for the BRUCE humanoid robot, developed by Westwood Robotics.
The application features seven possible reward functions. Note that we combine base_xyz_tracking and base_quat_tracking to explore a 6-dimensional objective space.
| Reward Name | Description |
|---|---|
gait_tracking |
Track the reference joint-level trajectory |
base_xyz_tracking |
Track the base position associated with the reference trajectory |
base_quat_tracking |
Track the base orientation associated with the reference trajectory |
arm_swinging |
Maximize the amount of arm-swing |
arm_static |
Minimize the amount of arm-swing |
minimize_energy |
Minimize energy consumption |
Examples of Multi-Objective Policies
| Policy | Result |
|---|---|
| Balanced Reward | |
| Max Imitation | |
| Max Arm Swinging | |
| Max Smoothness |
Citation
@article{janwani2026mo,
title={MO-Playground: Massively Parallelized Multi-Objective Reinforcement Learning for Robotics},
author={Janwani, Neil and Novoseller, Ellen and Lawhern, Vernon J and Tucker, Maegan},
journal={arXiv preprint arXiv:2603.09237},
year={2026}
}
Release files for moplayground 0.1.5
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| moplayground-0.1.5.tar.gz | 75.0 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| moplayground-0.1.5-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 164.8 kB
Release files / moplayground-0.1.5.tar.gz
| Download URL | moplayground-0.1.5.tar.gz |
|---|---|
| Size | 75.0 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
526c67e13e068990d057653da87365a4fb79b5428ca3924740d44d9f591e88f3
|
|
BLAKE2b-256 checksum How to use checksums |
9f517dea060bea887dfda3f64f156bfc292d5c2eda929f8dbb07db1c78854a93
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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 Sep 24, 2026.
Transparency logRelease files / moplayground-0.1.5-py3-none-any.whl
| Download URL | moplayground-0.1.5-py3-none-any.whl |
|---|---|
| Size | 89.9 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
4ec67f2a93ed858a24c080968f8bcb623747a9643b6f5b35a957156cec6e9e12
|
|
BLAKE2b-256 checksum How to use checksums |
3d30e144ce9f915942f453d4da36b8e1355638cfe98310cf9d0cbf373c0ba21c
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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 Sep 24, 2026.
Transparency log