Skip to main content

RoboVAST

Variation Automation and Scalable Testing for Robotic Systems.

Robot software that passes one demo has not been tested. RoboVAST takes your robotics stack — a Nav2 navigation setup, a manipulation pipeline, whatever drives your robot — and runs it through hundreds of simulated runs that differ in the ways that matter: floorplans, start and goal poses, obstacles, sensor noise, the parameters of the stack itself. Every run is recorded with its provenance, every campaign lands in a queryable index, and the results come back as tables, plots and a web view of each run rather than a directory of bags.

Framework Overview

What you get

  • Say what to vary, not how. A campaign is one file: which scenario, which factors, how many levels, how many repetitions. RoboVAST does the expansion, the scheduling and the bookkeeping.
  • One campaign, any cluster. The same file runs as jobs on a one-node cluster on your laptop or across a Kubernetes cluster. Nothing about the campaign changes; only where it runs and how fast it finishes.
  • Reproducible by construction. Pinned container images, recorded seeds and configuration, a run's full provenance beside its data. A result can be traced, and a campaign re-run.
  • A simulator by name. backend: roqsim gives you roqsim, a MuJoCo simulator for mobile robots, arms and mobile manipulators. Another simulator is another package.
  • Results you can ask questions of. Campaign data goes into a database; explore it in the web UI, in a notebook, or through an AI agent that can author, launch and analyse campaigns through the same interface you use.
  • Built on scenario-execution for the single run and the Floorplan-DSL for generated indoor environments. Mobile robot navigation is the reference use case, with a ready-made set of environments and scenarios to start from.

Install

pip install robovast-client              # drive a RoboVAST service someone runs for you
pip install "robovast[nav,roqsim]"       # the core: configuration, results, the MCP server
pip install robovast-cluster             # deploy and run the service on a Kubernetes cluster

Then vast cluster setup deploys the service — into minikube on your own machine, or a cluster for a team — and vast workspace run launches a campaign.

Documentation, from the quickstart to writing your own variation type or simulator backend: cps-test-lab.github.io/robovast.

Licence

Apache-2.0.

Metadata

Release files for robovast 2.2.1

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

Source distribution (sdist)

Source distribution for robovast 2.2.1
File Size Uploaded
robovast-2.2.1.tar.gz 1.2 MB Details

Built distribution (wheel)

Table of built distributions (wheels) for robovast 2.2.1
File Interpreter ABI Platform
robovast-2.2.1-py3-none-any.whl Python 3 none any Details

Total release size: 4.9 MB

Release files / robovast-2.2.1.tar.gz

Download URL robovast-2.2.1.tar.gz
Size 1.2 MB
Tags Source
SHA-256 checksum
How to use checksums
c7f29e729669aa1d9bf6b8c359afe7b98447a7dacaa63fe0aa6d6f352caf202e
BLAKE2b-256 checksum
How to use checksums
3120d765e2b5147f6ed1a2ebb5ed4f7c28edcd9c2e0a38fc928b0219172c3a44
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 10, 2026.

Transparency log

Release files / robovast-2.2.1-py3-none-any.whl

Download URL robovast-2.2.1-py3-none-any.whl
Size 3.7 MB
Tags Python 3
SHA-256 checksum
How to use checksums
f9337e2bcc20578cf1c342d1017ff290749851dd8ba864ab97c23957f7105b5b
BLAKE2b-256 checksum
How to use checksums
4f6366da9280d32b795b660d51dd26ca9da39b3e8759f408b2585a6d59661559
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 10, 2026.

Transparency log

Release history Release notifications | RSS feed

This release

2.2.1 This release

2 release files

2.2.0

2 release files

2.1.0

2 release files

1.0.0

2 release files

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