This release is a pre-release and may not be stable for production use.
Motrix RL
motrix-rl is MotrixLab's RL control plane. It provides framework-neutral training/playback orchestration, checkpoint and
run metadata services, backend selection, and the stable motrix_rl.frameworks registration/query entry point. Concrete
algorithm implementations are optional plugins, not implementation-owned modules in this package:
motrix-rl-builtin— built-inmotrix.fastsac(FastSAC)motrix-rl-skrl— SKRL PPO with JAX or PyTorchmotrix-rl-rslrl— RSLRL PPO with PyTorch
Plugins register through the motrix_rl.frameworks Python entry-point group when installed. The loader is invoked by
registry queries and explicitly before Hydra training-task composition; importing the control plane alone does not
hard-code plugin imports. Provider/trainer contracts live in motrix_rl.contracts inside this package.
The control plane has its own general runtime dependencies (including Torch); splitting provider packages does not make
motrix-rl itself a dependency-free package. motrix-rl never depends on provider plugins, including through optional
extras. The workspace root requires motrix-rl-builtin and motrix-rl-skrl, ensuring FastSAC and SKRL Torch are available
for the built-in demos. The root skrl-jax extra adds the JAX backend; rslrl adds the optional RSLRL plugin.
Runtime installation does not force other optional workspace packages.
Environment-specific training presets live under configs/task/, while shared provider defaults live under
configs/algo_base/. From the workspace root, select a preset with Hydra's task=<env-id>/<method> syntax (run from the
activated workspace environment, source .venv/bin/activate):
python scripts/train.py task=cartpole/skrl.ppo
python scripts/train.py task=cartpole/rslrl.ppo
python scripts/train.py task=g1-walk-rough/motrix.fastsac
Install the extra required by the selected provider before training:
sh install.sh --skrl-jax # JAX (Linux only)
sh install.sh --skrl-torch # PyTorch (default)
sh install.sh --rslrl # RSLRL (PyTorch only)
Metadata
Release files for motrix-rl 0.4.0b1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| motrix_rl-0.4.0b1-py3-none-any.whl | Python 3 | none | any | Details for motrix_rl-0.4.0b1-py3-none-any.whl |
Release files / motrix_rl-0.4.0b1-py3-none-any.whl
| Download URL | motrix_rl-0.4.0b1-py3-none-any.whl |
|---|---|
| Size | 51.2 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
45d0743146e76d5b112b7c1eae2c60ff3bf4590516fac1a182925aa9a1bdd679
|
|
BLAKE2b-256 checksum How to use checksums |
de819c4156b09028532ff123ab70d3ce7382bcc7a7b71142551733bc82e41fa0
|
| 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 Oct 12, 2026.
Transparency logSecurity for motrix-rl 0.4.0b1
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.
Full provenance
All 1 file in this release has been uploaded with provenance metadata.
Attestation for motrix_rl-0.4.0b1-py3-none-any.whl
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 Oct 12, 2026.
Transparency logA note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.