Skip to main content

RapidTag

PyPI version Python versions Wheels License: Apache-2.0 Release Built with Rust Platforms

⚠️ Work in progress — not production-ready. RapidTag is under active development and pre-1.0. APIs, behavior, and results may change without notice. Use it for research, evaluation, and prototyping, and validate it against your own data before relying on it for anything critical.

Fast, pure-Rust fiducial marker detection for realtime. RapidTag is a from-scratch Rust reimplementation of OpenCV's ArUco / AprilTag marker detector, exposed to Python via maturin / PyO3 — with no OpenCV runtime dependency. It reproduces OpenCV's detections down to the pixel while running substantially faster.

Why RapidTag

  • ⚡ Faster than OpenCV — ~1.6× faster for realtime single-camera detection, and up to ~3.4× faster for multi-camera and offline batches (scales across cores).
  • 🎯 A true drop-in for accuracy — corners match OpenCV to 0.0000 px, so any downstream pose or tracking is identical (see below).
  • 🧵 Scales with your cores — a batch API processes many frames (a stereo pair, or a whole recording) across all cores with the GIL released.
  • 📦 No OpenCV needed at runtime — the detection pipeline and marker dictionaries are implemented in pure Rust on top of image / nalgebra.

Performance

Measured on real dual-camera data (1280×800 monochrome, AprilTag 36h11):

Workload Speed vs OpenCV
Realtime, single camera 1.57× faster
Multi-camera / offline batch (all cores) up to ~3.4× faster

Same detections, less time — the speedup comes from a leaner detection pipeline, not from skipping work.

Heterogeneous (big.LITTLE) ARM CPUs

On big.LITTLE SoCs, RapidTag pins its worker pool to the fast cores automatically. Every detect call waits on its slowest parallel task, so letting the OS place even one task on a little core caps the whole batch at little-core speed — on a Radxa Dragon Q6A (QCS6490: 4× A55 @1.9 GHz + 4× A78 @2.4–2.7 GHz) auto-pinning takes a single 1280×800 detect from 68 fps to 211 fps, and a dual-camera pair from 66 to 134 pairs/s. The calling thread and any capture/IO threads are left unpinned, keeping the little cores for them. Homogeneous CPUs and non-Linux hosts are unaffected.

Override with RAPIDTAG_CORES: an explicit core list (4-7, 0,2,4) or all to disable pinning. RAYON_NUM_THREADS still controls pool size when set.

Two further board-level settings are worth it on embedded targets:

  • build for the exact CPU with scripts/build-board.sh (-C target-cpu=native)
  • switch the fast cores' cpufreq governor to performance — bursty per-frame work never keeps schedutil clocked up (on the Q6A this is another ~1.7×: 123 → 211 fps single, 102 → 134 pairs/s dual)

Accuracy — verified as a drop-in replacement

Because RapidTag's corners are pixel-identical to OpenCV's, feeding them into the exact same pose pipeline (cv2.solvePnP) yields the same trajectory. Across a ~1,700-frame stereo recording of a moving AprilTag, the recovered position from RapidTag vs OpenCV corners is indistinguishable — a median difference of 0.00 mm on both cameras.

OpenCV vs RapidTag pose comparison

Install

pip install rapidtag

Prebuilt wheels are published for:

OS Architectures libc
Linux x86_64, aarch64 (arm64) glibc (manylinux) + musl (Alpine)
macOS x86_64 (Intel), arm64 (Apple Silicon) —
Windows x64 —

Wheels are abi3 (one wheel works on CPython 3.9+). If no wheel matches, pip builds from the source distribution (needs a Rust toolchain).

Building from source in your own project (opt-in)

By default uv add rapidtag / pip install rapidtag install the prebuilt portable wheel — no Rust toolchain needed. There is no package-side flag or extra (e.g. rapidtag[native]) that changes this; forcing a source build is always an installer-side opt-in on your side, and it needs a Rust toolchain (rustc/cargo) installed.

To make your project always compile rapidtag from source, add this to your pyproject.toml before installing:

[tool.uv]
no-binary-package = ["rapidtag"]

Then, to get CPU-native codegen for the machine you're installing on, set RUSTFLAGS at install time:

RUSTFLAGS="-C target-cpu=native" uv sync

Without RUSTFLAGS this still compiles a portable binary — functionally the same as the prebuilt wheel, just slower to install. The target-cpu=native build is not portable; don't redistribute it.

pip equivalents: pip install rapidtag --no-binary rapidtag, optionally prefixed with the same RUSTFLAGS.

Usage

import cv2            # only to load/generate images
import rapidtag

img = cv2.imread("scene.png")          # HxWx3 BGR, or HxW grayscale uint8

# --- realtime: one frame ---
corners, ids = rapidtag.detect_markers(img, "DICT_APRILTAG_36h11")
# corners: list of 4x2 [(x, y), ...] per marker (clockwise)
# ids:     list of marker ids, aligned with corners

# --- multi-camera / batch: process many frames across all cores ---
results = rapidtag.detect_markers_batch([cam0, cam1], "DICT_APRILTAG_36h11")
(c0, i0), (c1, i1) = results

# --- tunable parameters (same names/defaults as cv2.aruco.DetectorParameters) ---
p = rapidtag.DetectorParameters()
p.adaptive_thresh_constant = 7.0
p.detect_inverted_marker = True
corners, ids = rapidtag.detect_markers(img, "DICT_6X6_250", p)

print(rapidtag.predefined_dictionaries())   # list supported dictionary names

# --- generic calibration chessboard (9 columns x 6 rows of interior corners) ---
found, chessboard_corners = rapidtag.find_chessboard_corners(img, (9, 6))

# --- robust board / multi-marker pose with bad-correspondence rejection ---
pose = rapidtag.solve_pnp_ransac(
    object_points, image_points, camera_matrix, dist_coeffs,
    iterations=100, reprojection_error=3.0, confidence=0.99, seed=0,
)
if pose is not None:
    rvec, tvec, inlier_indices, reprojection_rmse = pose

# --- reusable rigid-body geometry; construct once from your calibration ---
marker_ids = sorted(int(marker_id) for marker_id in rigid_body_config["markers"])
body = rapidtag.RigidBody(
    rigid_body_config["meta"]["tag_size_m"],
    marker_ids,
    [rigid_body_config["markers"][str(i)]["rotation_marker_to_reference"]
     for i in marker_ids],
    [rigid_body_config["markers"][str(i)]["translation_marker_to_reference_m"]
     for i in marker_ids],
)
body_pose = rapidtag.estimate_rigid_body_pose(
    corners, ids, body, camera_matrix, dist_coeffs,
    iterations=100, reprojection_error=3.0,
)
if body_pose is not None:
    print(body_pose.rvec, body_pose.tvec)
    print(body_pose.used_marker_ids, body_pose.inlier_marker_ids)

Documentation

Python signatures are also shipped in rapidtag.pyi for IDEs and type checkers. Maintainers can build the internal Rust documentation with cargo doc --no-deps --document-private-items --open.

Supported dictionaries: all DICT_{4,5,6,7}X{4,5,6,7}_{50,100,250,1000}, DICT_ARUCO_ORIGINAL, DICT_ARUCO_MIP_36h12, and AprilTag DICT_APRILTAG_{16h5,25h9,36h10,36h11}.

Status

Implemented:

  • ArUco / AprilTag marker detection (detectMarkers, CORNER_REFINE_NONE)
  • Generic chessboard detection with sub-pixel corners (findChessboardCorners)
  • ChArUco board detection using local marker homographies
  • Iterative PnP, RANSAC PnP, rigid-body multi-marker pose, Rodrigues, point projection, and ChArUco board pose estimation

Not yet implemented: marker-corner refinement, grid boards, camera calibration, refineDetectedMarkers, and ChArUco's camera-aware interpolation path.

Build from source

maturin develop --release        # dev install into the current virtualenv
maturin build --release          # or build a wheel

The committed build uses portable CPU baselines so one wheel works everywhere. For a max-performance build tuned to your own machine (not portable — don't redistribute it):

RUSTFLAGS="-C target-cpu=native" maturin build --release

For a wheel tuned to a specific ARM64 board, use ./scripts/build-board.sh (it picks the right CPU flags so the published portable wheels stay CPU-agnostic).

Tests

python tests/crosscheck.py     # cross-validate vs cv2.aruco on synthetic scenes
python tests/crosscheck_chessboard.py  # generic chessboard parity vs OpenCV
python tests/crosscheck_charuco.py     # ChArUco parity vs OpenCV
python tests/crosscheck_pnp.py         # geometry and end-to-end pose parity
python tests/bench.py          # benchmark + parity on real camera data
python scripts/bench_ransac_dome.py    # multi-marker RANSAC benchmark on dome recordings

The verification figures above are reproduced by the scripts in scripts/ (pnp_opencv_vs_rapidtag.py, pnp_sanity.py).

Release files for rapidtag 0.1.7

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

Source distribution (sdist)

Source distribution for rapidtag 0.1.7
File Size Uploaded
rapidtag-0.1.7.tar.gz 1.0 MB Details

Built distributions (wheels)

Table of built distributions (wheels) for rapidtag 0.1.7
File
rapidtag-0.1.7-cp39-abi3-win_amd64.whl CPython 3.9 abi3 Windows x86-64 Details
rapidtag-0.1.7-cp39-abi3-musllinux_1_2_x86_64.whl CPython 3.9 abi3 Linux musl 1.2+ x86-64 Details
rapidtag-0.1.7-cp39-abi3-musllinux_1_2_aarch64.whl CPython 3.9 abi3 Linux musl 1.2+ ARM64 Details
rapidtag-0.1.7-cp39-abi3-manylinux_2_17_x86_64.manylinux2014_x86_64.whl CPython 3.9 abi3 Linux glibc 2.17+ x86-64 Details
rapidtag-0.1.7-cp39-abi3-manylinux_2_17_aarch64.manylinux2014_aarch64.whl CPython 3.9 abi3 Linux glibc 2.17+ ARM64 Details
rapidtag-0.1.7-cp39-abi3-macosx_11_0_arm64.whl CPython 3.9 abi3 macOS 11.0+ ARM64 Details
rapidtag-0.1.7-cp39-abi3-macosx_10_12_x86_64.whl CPython 3.9 abi3 macOS 10.12+ x86-64 Details

Total release size: 6.3 MB

Release files / rapidtag-0.1.7.tar.gz

Download URL rapidtag-0.1.7.tar.gz
Size 1.0 MB
Tags Source
SHA-256 checksum
How to use checksums
6d9b1df337672a9edecb2590b5ae80584c7bcf7028a6a4930b9659b78f3ed7b4
BLAKE2b-256 checksum
How to use checksums
1f0a2f577b09dc782b85e8d718825794fa58ee6aaef4421e73b0f0d7b43b360a
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 25, 2026.

Transparency log

Release files / rapidtag-0.1.7-cp39-abi3-win_amd64.whl

Download URL rapidtag-0.1.7-cp39-abi3-win_amd64.whl
Size 605.0 kB
Tags CPython 3.9 Windows x86-64 abi3
SHA-256 checksum
How to use checksums
87fa96b9b53fa297eaf2caae6ff3f7e1094ff4146cbd866811bd920900ddc842
BLAKE2b-256 checksum
How to use checksums
76338c57b7a306a4a644a6aac61053c667ffaa099011983acda6a4bbf43f5252
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 25, 2026.

Transparency log

Release files / rapidtag-0.1.7-cp39-abi3-musllinux_1_2_x86_64.whl

Download URL rapidtag-0.1.7-cp39-abi3-musllinux_1_2_x86_64.whl
Size 946.0 kB
Tags CPython 3.9 Linux musl 1.2+ x86-64 abi3
SHA-256 checksum
How to use checksums
e7195f07cce348de83916e02b21ce9956c74212abf511b9004aea79c40f16bf1
BLAKE2b-256 checksum
How to use checksums
57ba82dede105fa21b131015855a115966b5d1191775852a7d99b1a4fa06c084
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 25, 2026.

Transparency log

Release files / rapidtag-0.1.7-cp39-abi3-musllinux_1_2_aarch64.whl

Download URL rapidtag-0.1.7-cp39-abi3-musllinux_1_2_aarch64.whl
Size 889.8 kB
Tags CPython 3.9 Linux musl 1.2+ ARM64 abi3
SHA-256 checksum
How to use checksums
51a3efeccceb0a32ce8e458200db0d2bd64709588b20dedb0d31f38ebb8c8944
BLAKE2b-256 checksum
How to use checksums
85db6974dddeb1e89354b964d7ee9802700092620a8c37ea5e9c5e704fdb8abf
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 25, 2026.

Transparency log

Release files / rapidtag-0.1.7-cp39-abi3-manylinux_2_17_x86_64.manylinux2014_x86_64.whl

Download URL rapidtag-0.1.7-cp39-abi3-manylinux_2_17_x86_64.manylinux2014_x86_64.whl
Size 733.0 kB
Tags CPython 3.9 Linux glibc 2.17+ x86-64 abi3
SHA-256 checksum
How to use checksums
a4c773d3bc4dd0d5bbda33959db0a4cfa5232072d8ae8f41d3044ac0d75f9f82
BLAKE2b-256 checksum
How to use checksums
21cee90d29cbc8ad9db16266c7bcc6a4cfd0f251ed9ad1faefcdeb3597e7a027
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 25, 2026.

Transparency log

Release files / rapidtag-0.1.7-cp39-abi3-manylinux_2_17_aarch64.manylinux2014_aarch64.whl

Download URL rapidtag-0.1.7-cp39-abi3-manylinux_2_17_aarch64.manylinux2014_aarch64.whl
Size 712.3 kB
Tags CPython 3.9 Linux glibc 2.17+ ARM64 abi3
SHA-256 checksum
How to use checksums
4a60724a56d04f82377d16dc06f52d94d7b3fd12ea2299533301f162cdd2dd44
BLAKE2b-256 checksum
How to use checksums
30770b560383bcf1db202b128ea6a4c0731464e15f5976883db292f3adbc10b6
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 25, 2026.

Transparency log

Release files / rapidtag-0.1.7-cp39-abi3-macosx_11_0_arm64.whl

Download URL rapidtag-0.1.7-cp39-abi3-macosx_11_0_arm64.whl
Size 664.7 kB
Tags CPython 3.9 abi3 macOS 11.0+ ARM64
SHA-256 checksum
How to use checksums
956634ab11309f0b231fb4df90fda9beedefd974b5eaa52533fe1aaa7e7c2666
BLAKE2b-256 checksum
How to use checksums
e2ab25843efd46cb61ce24cc0a189e7edb562acbd5928aee00e3e765d0faa24b
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 25, 2026.

Transparency log

Release files / rapidtag-0.1.7-cp39-abi3-macosx_10_12_x86_64.whl

Download URL rapidtag-0.1.7-cp39-abi3-macosx_10_12_x86_64.whl
Size 688.3 kB
Tags CPython 3.9 abi3 macOS 10.12+ x86-64
SHA-256 checksum
How to use checksums
09943d04ed5117af0f26e1172ba75948885773004555549f9312b12f009614e6
BLAKE2b-256 checksum
How to use checksums
9991b3833818a1a2d2fef238f5178dfe84631bad15ba957ee44dd4f7bd08e644
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 25, 2026.

Transparency log

Release history Release notifications | RSS feed

This release

0.1.7 This release

8 release files

0.1.5

8 release files

0.1.4

8 release files

0.1.3

8 release files

0.1.0

8 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