OopsieData Tools
Oopsie Data is an initative to build a large-scale dataset of real robot manipulation failures (along with other mixed-quality behaviors and successes). Oopsie Data Tools helps labs record, annotate, and contribute those rollouts instead of throwing them away.
Ready to contribute? Start with the Quickstart Guide.
For documentation, contribution instructions, and tooling guides, visit our website.
This repository currently provides tools for:
- HDF5 episode recording (
EpisodeRecorder) - Web annotation workflows
- In-the-loop annotation during policy rollout
as well as all the necessary utilities to validate, quality-check (oopsie-data qa), inspect, and upload Oopsie-Data to the official repositories.
Need help integrating?
Open an issue if you need help adding Oopsie Tools recording to your eval pipeline. Include your robot platform, policy stack, and a pointer to your evaluation/inference code.
1 maintainer
Metadata
1 maintainer
Release files for oopsie-data-tools 1.2.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| oopsie_data_tools-1.2.0.tar.gz | 2.5 MB | With provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| oopsie_data_tools-1.2.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 2.8 MB
Release files / oopsie_data_tools-1.2.0.tar.gz
| Download URL | oopsie_data_tools-1.2.0.tar.gz |
|---|---|
| Size | 2.5 MB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
b57448b65201de66e4e0c2a386525c2f8eceab384424388a9f36b1a5d3798436
|
|
BLAKE2b-256 checksum How to use checksums |
c805ef4c094185838704b95cccc1e6ac234ee19192d94dd9211c19b4ded9b938
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
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 23, 2026.
Transparency logRelease files / oopsie_data_tools-1.2.0-py3-none-any.whl
| Download URL | oopsie_data_tools-1.2.0-py3-none-any.whl |
|---|---|
| Size | 281.2 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
46caa5d94f99c3ffb3bc8f0c358c1beffd3bdcdb6826b531b30871f521143105
|
|
BLAKE2b-256 checksum How to use checksums |
9957736d2079d5581993f41397e2fa38fee1d0c5e6e287726e066f2ced2bcbde
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
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 23, 2026.
Transparency logSecurity for oopsie-data-tools 1.2.0
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 2 files in this release have been uploaded with provenance metadata.
Attestation for oopsie_data_tools-1.2.0.tar.gz
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 23, 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.
