The Tactile MNIST Active Perception Benchmark Suite
|
TactileMNIST-v0 |
Starstruck-v0 |
Toolbox-v0 |
|
ABCCenterOfMass-v0 |
TactileMNISTVolume-v0 |
ABCVolume-v0 |
|
Minecraft-v0 |
MinecraftPose-v0 |
Tactile MNIST is a benchmark for learning-based active perception algorithms. It introduces nine simulated tactile perception tasks, ranging from classification and counting to pose, center of mass, and volume estimation. Each task comes with a unique set of challenges and, thus, Tactile MNIST requires adaptive algorithms and clever exploration strategies. The aim of Tactile MNIST is to provide an extensible framework for a fair comparison of active tactile perception methods.
Tactile MNIST implements each task as an ap_gym environment and is, thus, very straightforward to set up and use. In each task, the agent controls a single simulated GelSight Mini above a platform with some task-specific objects. The agent's objective is to make a prediction about some property of the objects it is exploring, such as their class, count, pose, or volume.
In addition to the simulated benchmark tasks, this package provides access to a large dataset of real tactile images collected from 3D printed MNIST digits and a couple of synthetic datasets.
Further details can be found on our project page, which also links to the paper.
Installation
Install Tactile MNIST via pip:
pip install tactile-mnist[OPTIONS]
where OPTIONS can be any number of the following (comma separated):
examples: installs dependencies for the examples.jax(recommended) ,torch, andjax-cpu: installs dependencies for the interactive Tactile MNIST environment with PyTorch, JAX, or JAX without CUDA support, respectively. Without any of those options, the interactive environment cannot be used but the static datasets will still work.
If you encounter problems during the installation or execution, check our troubleshooting section.
Contents
This package provides ap_gym environments for nine simulated active tactile perception benchmark tasks and access to the Tactile MNIST datasets. The ap_gym environments can be used to train and evaluate agents on active tactile perception problems on simulated data and are further described in the Benchmark section. In the Tactile MNIST datasets, you find datasets of 3D CAD models (MNIST 3D, the procedurally generated Starstruck, and ABC) and several datasets of simulated and real tactile images. This package provides an easy way of loading and working with these datasets, as further described in the Datasets section.
Simulated Active Tactile Perception Benchmark
This package provides ap_gym environments for nine active tactile perception environments: TactileMNIST, Starstruck, Minecraft, Toolbox, MinecraftPose, TactileMNISTCenterOfMass, ABCCenterOfMass, TactileMNISTVolume, and ABCVolume. In all environments, the agent must solve a perception problem by actively controlling a GelSight Mini tactile sensor in a simulated environment.
The TactileMNIST environment challenges the agent to find and classify a 3D MNIST model as quickly as possible. aside from finding the object, the main challenge in the TactileMNIST environment is to learn contour following strategies to efficiently classify it once found.
In the Starstruck environment, the agent must count the number of stars in a scene cluttered with other objects. Since all stars look the same, distinguishing stars from other objects is rather straightforward. Instead, the main challenge posed in this environment is to learn an effective search strategy to systematically cover as much space as possible. The scenes are generated procedurally on the fly from a stable pseudo random number generator, so the agent cannot memorize the object arrangements.
The Minecraft environment poses a classification problem over 299 classes of Minecraft items, whose meshes are generated by extruding the items' sprites the same way Minecraft renders dropped items. With over 30 times more classes than TactileMNIST, the agent has to discriminate between a large number of partially very similar silhouettes, which requires precise contour following and efficient exploration.
The Toolbox environment challenges the agent to locate a wrench positioned randomly on a platform and estimate its precise 2D position and 1D orientation. Unlike the previous classification tasks, Toolbox poses a regression problem that requires combining multiple touch observations to resolve ambiguities inherent in the wrench’s shape. For example, touching the handle may reveal lateral placement but not longitudinal position or orientation, making it critical for the agent to explore strategically and seek out one of the wrench’s ends to accurately determine its pose. Overall, the Toolbox tests the agent’s ability to both find and precisely localize an object through sequential tactile exploration.
The MinecraftPose environment poses the same pose estimation problem as Toolbox, except that the object is sampled from 299 different Minecraft items in each episode instead of always being the same wrench. Hence, the agent has to learn exploration strategies that generalize across a large variety of object shapes.
In the TactileMNISTCenterOfMass and ABCCenterOfMass environments, the agent must determine the exact 2D position of the center of mass of an object from the 3D MNIST and ABC datasets, respectively. Unlike in the Toolbox environment, where the object shape is known, in TactileMNISTCenterOfMass and ABCCenterOfMass, the agent has to deal with a large variety of object shapes and learn thorough exploration policies. Due to the larger variety of object shapes in the ABC dataset, we give the agent control over the sensor's rotation in ABCCenterOfMass, which adds another layer of complexity to the problem.
The TactileMNISTVolume environment poses another regression problem. Here, the agent must determine the exact volume of the 3D MNIST model it is given. Thus, unlike in the TactileMNIST environment, where a couple of touches might already be sufficient for classification, in TactileMNISTVolume, the agent has to make sure to explore the entire object.
Similar to the TactileMNISTVolume environment, the ABCVolume environment challenges the agent to determine the exact volume of an object. However, instead of 3D MNIST models, the objects in ABCVolume are randomly sampled from the ABC dataset, which contains a large variety of 3D CAD models. Similar to ABCCenterOfMass, we give the agent control over the sensor's rotation in ABCVolume.
A detailed description of the environments can be found here.
Datasets
Aside of the simulated benchmark tasks, this package provides access to two classes of datasets: 3D mesh datasets and touch datasets. Below is an overview of the datasets provided in this package:
- 3D Mesh Datasets:
- MNIST 3D: a dataset of 3D models generated from a high-resolution version of the MNIST dataset.
- Starstruck: a procedurally generated dataset in which the number of stars in a scene has to be counted (3 classes, 1 - 3 stars per scene).
- ABC Dataset: a variant of the ABC dataset, processed for the use with this benchmark suite.
- Touch Datasets
- Synthetic Tactile MNIST: a dataset of synthetic tactile images generated from the MNIST 3D dataset with the Taxim simulator.
- Real Tactile MNIST: a dataset of real tactile images of 3D printed MNIST 3D digits collected with a Franka robot.
- Synthetic Tactile Starstruck: a dataset of synthetic tactile images generated from a static version of the Starstruck dataset with the Taxim simulator.
A detailed description of the datasets can be found in the Dataset documentation.
Troubleshooting
Torch-Scatter Undefined Symbol Error
If you are seeing errors as such
OSError: [...]/torch_scatter/_version_cpu.so: undefined symbol: _ZN3c1017RegisterOperatorsD1Ev
then there are CUDA version incompatibilities between torch_scatter, PyTorch, and nvcc.
If you are seeing errors as such
RuntimeError: Not compiled with CUDA support
then nvcc was not found when installing torch_scatter.
In both cases, follow the instructions in the official torch_scatter repository to install compatible PyTorch and torch_scatter versions.
License
The project is licensed under the MIT license.
Contributing
If you wish to contribute to this project, you are welcome to create a pull request. Please run the pre-commit hooks before submitting your pull request. To install the pre-commit hooks, run:
- Install pre-commit
- Install the Git hooks by running
pre-commit installor, alternatively, run `pre-commit run --all-files manually.
Metadata
Release files for tactile-mnist 0.13.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 | |
|---|---|---|---|
| tactile_mnist-0.13.0.tar.gz | 85.3 MB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| tactile_mnist-0.13.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 170.5 MB
Release files / tactile_mnist-0.13.0.tar.gz
| Download URL | tactile_mnist-0.13.0.tar.gz |
|---|---|
| Size | 85.3 MB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
8b3475c025406830ee8976da2a6f165984cb3fce132cb5fd1566eaf0486912ae
|
|
BLAKE2b-256 checksum How to use checksums |
70d8b62b7b4e5c02c18893d06f7ac8638d947d10ac94c0e9a9f65b69cbad28b5
|
| 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 logRelease files / tactile_mnist-0.13.0-py3-none-any.whl
| Download URL | tactile_mnist-0.13.0-py3-none-any.whl |
|---|---|
| Size | 85.3 MB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
308e854328c28d37966fc96353f713dc6cf4ae3131fb9b7c1374fac9b3544cb5
|
|
BLAKE2b-256 checksum How to use checksums |
3e734ba9df8be30fe56ed8d85ef3d5c90496d22501969b2885f1cff800db48f2
|
| 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 log