pupil-apriltags: Python bindings for the apriltags3 library
These are Python bindings for the Apriltags3 library developed by AprilRobotics, specifically adjusted to work with the pupil-labs software. The original bindings were provided by duckietown and were inspired by the Apriltags2 bindings by Matt Zucker.
How to get started:
Install from PyPI
This is the recommended and easiest way to install pupil-apriltags.
pip install pupil-apriltags
We offer pre-built binary wheels for common operating systems. In case your system does not match, the installation might take some time, since the native library (apriltags-source) will be compiled first.
Manual installation from source (for development)
You can of course clone the repository and build from there. For development you should install the development requirements as well. This project uses the new python build system configuration from PEP 517 and PEP 518.
# clone the repository
git clone https://github.com/pupil-labs/apriltags.git
cd apriltags
# install apriltags in editable mode with development requirements
pip install -e .[dev]
# run tests
tox
Usage
Some examples of usage can be seen in the src/pupil_apriltags/bindings.py file.
The Detector class is a wrapper around the Apriltags functionality. You can initialize it as following:
from pupil_apriltags import Detector
at_detector = Detector(searchpath=['apriltags'],
families='tag36h11',
nthreads=1,
quad_decimate=1.0,
quad_sigma=0.0,
refine_edges=1,
decode_sharpening=0.25,
debug=0)
The options are:
| Option | Default | Explanation |
|---|---|---|
| families | 'tag36h11' | Tag families, separated with a space |
| nthreads | 1 | Number of threads |
| quad_decimate | 2.0 | Detection of quads can be done on a lower-resolution image, improving speed at a cost of pose accuracy and a slight decrease in detection rate. Decoding the binary payload is still done at full resolution. Set this to 1.0 to use the full resolution. |
| quad_sigma | 0.0 | What Gaussian blur should be applied to the segmented image. Parameter is the standard deviation in pixels. Very noisy images benefit from non-zero values (e.g. 0.8) |
| refine_edges | 1 | When non-zero, the edges of the each quad are adjusted to "snap to" strong gradients nearby. This is useful when decimation is employed, as it can increase the quality of the initial quad estimate substantially. Generally recommended to be on (1). Very computationally inexpensive. Option is ignored if quad_decimate = 1 |
| decode_sharpening | 0.25 | How much sharpening should be done to decoded images? This can help decode small tags but may or may not help in odd lighting conditions or low light conditions |
| searchpath | ['apriltags'] | Where to look for the Apriltag 3 library, must be a list |
| debug | 0 | If 1, will save debug images. Runs very slow |
Detection of tags in images is done by running the detect method of the detector:
tags = at_detector.detect(img, estimate_tag_pose=False, camera_params=None, tag_size=None)
If you also want to extract the tag pose, estimate_tag_pose should be set to True and camera_params ([fx, fy, cx, cy]) and tag_size (in meters) should be supplied. The detect method returns a list of Detection objects each having the following attributes (note that the ones with an asterisks are computed only if estimate_tag_pose=True):
| Attribute | Explanation |
|---|---|
| tag_family | The family of the tag. |
| tag_id | The decoded ID of the tag. |
| hamming | How many error bits were corrected? Note: accepting large numbers of corrected errors leads to greatly increased false positive rates. NOTE: As of this implementation, the detector cannot detect tags with a Hamming distance greater than 2. |
| decision_margin | A measure of the quality of the binary decoding process: the average difference between the intensity of a data bit versus the decision threshold. Higher numbers roughly indicate better decodes. This is a reasonable measure of detection accuracy only for very small tags-- not effective for larger tags (where we could have sampled anywhere within a bit cell and still gotten a good detection.) |
| homography | The 3x3 homography matrix describing the projection from an "ideal" tag (with corners at (-1,1), (1,1), (1,-1), and (-1, -1)) to pixels in the image. |
| center | The center of the detection in image pixel coordinates. |
| corners | The corners of the tag in image pixel coordinates. These always wrap counter-clock wise around the tag. |
| pose_R* | Rotation matrix of the pose estimate. |
| pose_t* | Translation of the pose estimate. |
| pose_err* | Object-space error of the estimation. |
Custom layouts
If you want to use a custom layout, you need to create the C source and header files for it and then build the library again. Then use the new libapriltag.so library. You can find more information on the original Apriltags repository.
1 maintainer
Metadata
1 maintainer
Release files for pupil-apriltags 1
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 | Actions |
|---|---|---|---|---|
| pupil-apriltags-1.tar.gz | 1.9 MB | Without provenance | Details for pupil-apriltags-1.tar.gz |
Built distributions (wheels)
Total release size: 39.4 MB
Security for pupil-apriltags 1
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.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A 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.
