aimio-py
Python bindings for the Numerics88 AimIO C++ library.
aimio-py provides a small Python API to read and write AIM files as NumPy arrays, read ISQ, SCV, GOBJ, RAD, and RSQ files, inspect metadata, and work with processing logs.
Features
- Read AIM files into NumPy arrays
- Write AIM files from NumPy arrays
- Read ISQ files into NumPy arrays
- Read SCV scout-view files into NumPy arrays
- Read native RAD radiographs with header-derived mm spacing
- Read GOBJ contour masks into binary NumPy volumes
- Read AIM, ISQ, SCV, GOBJ, RAD, or RSQ files with single
read_imageandimage_infodispatchers - Read RSQ raw detector projections with optional read-only memory mapping
- Access format-specific header metadata (
aim_info,isq_info,scv_info,gobj_info,rad_info,rsq_info) - Convert processing logs between text and dictionary formats
- Optional density/HU conversion helpers
Installation
From PyPI (recommended):
pip install aimio-py
From source:
git clone https://github.com/wallematthias/aimio-py.git
cd aimio-py
git submodule update --init --recursive
pip install -e .
Quickstart
from py_aimio import image_info, read_image, write_aim
array, meta = read_image("scan.AIM")
print(meta["origin"], meta["spacing"], meta["direction"])
header = image_info("scan.AIM")
write_aim("copy.AIM", array, meta)
The matching metadata CLI uses the same format resolution:
aimio-info scan.AIM
aimio-info mask.GOBJ --format gobj
aimio-info projections.RSQ --format rsq
aimio-info scout.RAD --format rad
Reading Options
read_image() detects AIM, ISQ, SCV, GOBJ, RAD, and RSQ files from the extension and
forwards any extra keyword arguments to the format-specific reader.
aim, aim_meta = read_image("scan.AIM", density=True)
isq, isq_meta = read_image("scan.ISQ", unit="density")
scout, scout_meta = read_image("scout.SCV")
radiograph, rad_meta = read_image("scout.RAD")
mask, mask_meta = read_image("mask.GOBJ", value=1, crop="tight")
counts, rsq_meta = read_image("projections.RSQ", mmap=True)
The format-specific readers are also available directly:
- AIM:
read_aim(path, density=False, hu=False) - ISQ:
read_isq(path, unit="native"), whereunitcan be"native","hu","density", or"bmd" - SCV:
read_scv(path) - RAD:
read_rad(path) - GOBJ:
read_gobj(path, value=127, crop="tight"), wherecropcan be"tight"or"header" - RSQ:
read_rsq(path, *, mmap=False)
At the moment, AIM and ISQ default to native stored values. For calibrated bone
workflows, request density/BMD explicitly with density=True for AIM or
unit="density"/unit="bmd" for ISQ.
API
read_image(path, format="auto", **kwargs) -> (array, meta)image_info(path, format="auto") -> meta
Format-specific readers and metadata helpers are also available:
read_aim(path, density=False, hu=False) -> (array, meta)read_isq(path, unit="native") -> (array, meta)read_scv(path) -> (array, meta)read_rad(path) -> (array, meta)read_gobj(path, value=127, crop="tight") -> (array, meta)read_rsq(path, *, mmap=False) -> (counts, meta)aim_info(path),isq_info(path),scv_info(path),gobj_info(path),rad_info(path),rsq_info(path)write_aim(path, array, meta=None, unit=None)get_aim_density_equation(processing_log)get_aim_hu_equation(processing_log)log_to_dict(log)dict_to_log(dct)
Read metadata includes SimpleITK-style geometry keys for both AIM and ISQ:
origin, spacing, and direction. For AIM, spacing is copied from
element_size and origin follows the ITKIOScanco-compatible convention:
(position + offset) * spacing. The older vtkbone-style half-voxel-shifted
origin is also exposed as vtkbone_origin. For ISQ, spacing comes from the ISQ
header and origin defaults to (0.0, 0.0, 0.0). direction currently defaults
to the 3D identity direction, matching the practical behavior observed from
ITKIOScanco for ISQ files without explicit orientation metadata.
GOBJ files are read as contour masks. Additive contours are rasterized as
filled contours including their boundary. Subtractive contours, such as inner
cortical boundaries, remove only the strict contour interior so the contour
boundary remains part of the mask. crop="tight" returns the contour bounding
box, while crop="header" returns the full CTDATA header grid.
SCV scout readers accept both stream exports and binary extracts that retain
VMS variable-length record wrappers. RMS length words and odd-record alignment
bytes are skipped in memory; the source file is never rewritten. Outer record
lengths must match the enclosed SCV profiles. Metadata reports storage_format
(stream or vms_variable_records), and record/payload offsets refer to the
original file, including any wrappers.
SCV profile records contain a two-byte marker, a VMS F-floating row coordinate,
a compressed-byte count, and the complete run-length-encoded pixel row.
The first two compressed bytes are pixels, not a separate horizontal offset.
Each decoded row must match the declared width; truncated runs and excess
records are rejected. The aux and phase fields remain raw compatibility
metadata, not geometry parameters.
The historical SCV spacing/origin convention matches IPL's scv_to_aim
output for the paired reference scout. This does not establish calibrated
physical geometry for every scanner variant: scouts with repeated/nonuniform
row coordinates or invalid extents load with unit spacing and zero origin in
pixel space, with a warning. geometry_unit, geometry_source, and
geometry_warning identify this fallback; row_positions_mm and
header_spacing retain the original information. Do not use pixel-space scouts
for physical measurements or registration. Stripping VMS wrappers alone does
not repair such geometry.
RAD radiographs
read_rad(path) returns a native signed-int16 2D array in (row, column)
order; rad_info(path) inspects the header and validates storage without loading
pixels. The pure-Python reader supports CTDATA-HEADER_V1, type-9 radiographs,
including extra header blocks and optional zero padding to the next 512-byte
boundary. The source file is never rewritten.
RAD physical dimensions are nanometres, unlike ISQ's micrometres. Metadata
converts them to mm in physical_dimensions_mm, spacing, and element_size;
dimensions is (width, height, 1), and the placeholder third-axis spacing is
1 mm, not a measured slice thickness. origin=(0,0,0) and identity direction
describe a standalone display plane, not co-registration with CT.
z_position_mm, reference_line_mm, and scan start/end positions are retained
separately. No HU/density conversion is supported for this projection image.
Header interpretation follows the RAD branch of David Gobbi's vtk-dicom Scanco reader.
RSQ raw projections
from py_aimio import read_rsq, rsq_info
counts, meta = read_rsq("projections.RSQ;1", mmap=True)
print(counts.shape, meta["axis_order"])
header = rsq_info("projections.RSQ;1")
The supported RSQ storage interpretation uses the 16-byte
CTDATA-HEADER_V1 magic and 128 little-endian unsigned header words. Arrays
have shape (header_words[13], header_words[12], header_words[11]) and axes
("detector_row", "frame", "detector_column"). Values are decoded as
little-endian unsigned 16-bit detector counts (<u2), preserving values up to
65535. Signedness has not been independently confirmed for every proprietary
Scanco RSQ variant. mmap=True returns a read-only NumPy memory map.
Every stored frame is retained. Object views and any reference frames are not
classified or discarded, and raw reading does not require a minimum number of
frames. RSQ projections do not carry reconstructed volume origin, spacing,
or direction keys. Spatial volume, HU, and density conversion requests through
read_image() raise ValueError.
Metadata includes header_words, shape, axis_order, dtype,
data_offset_bytes, and a geometry dictionary with explicit provenance and
header positions. Geometry hints include requested output pitch and axial start
in micrometers, native detector dimensions, detector size, source distances,
binning, object view count, and angular interval in millidegrees. These are
partially inferred header meanings, not independently validated reconstruction
geometry. Words 21 and 22 are exposed as count_range; they do not define
attenuation scaling. Patient-name fields are not decoded, although raw header
words can still contain identifying data.
Both readers validate positive dimensions and require a detector payload length
of 2 * product(shape) bytes after offset 512 * (header_words[127] + 1).
An optional zero-filled tail extending exactly to the next 512-byte boundary
is accepted for VMS block-aligned extracts and reported as padding_size_bytes.
Unsupported magic, truncated data, nonzero padding, and other trailing bytes
are rejected. rsq_info() checks file size and reads only the base header,
final 512-byte header block, and any padding, not detector counts.
When that block contains a recognized Beamhard.Corr. title,
three float64 coefficients at bytes 476:500 are checked against the printed
Corr at 2 3 6: anchors using
delta(p) = a1*p + a2*p**2 + a3*p**3 with absolute tolerance 1e-6.
Corrupt recognized calibration raises ValueError; absent or unrecognized
calibration has beam_hardening["available"] = False. The reader exposes
validated coefficients without applying them to counts.
Development
Run tests:
pytest -q
Run tests with coverage:
pytest -q --cov=py_aimio --cov-report=term-missing --cov-report=xml:coverage.xml
Build local artifacts:
python -m build --wheel --sdist
Build documentation from docstrings:
pip install sphinx
make -C docs html
Generated HTML will be in docs/build/html/index.html.
Important build note
This project depends on the external/AimIO and external/n88util git submodules. If they are missing, extension builds will fail.
Attribution
py_aimio/calibration.pyis adapted from Bonelab/Bonelab.py_aimio/header_log.pyis by Matthias Walle.py_aimio/scv.pyandpy_aimio/gobj.pyare by Matthias Walle and Andrew Burghardt.
License
MIT
Metadata
Release files for aimio-py 0.4.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 | |
|---|---|---|---|
| aimio_py-0.4.1.tar.gz | 82.5 kB | Details |
Built distributions (wheels)
Total release size: 14.1 MB
Release files / aimio_py-0.4.1.tar.gz
| Download URL | aimio_py-0.4.1.tar.gz |
|---|---|
| Size | 82.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
4b8e9786e753aa17e522877f26eab2201ef2b676f5bf499ad645d1a345a287e8
|
|
BLAKE2b-256 checksum How to use checksums |
1ddc1a7b54de3ec4940f4c847ff2aa1d60ed060b4e8ec2a59cd42bbbf3fd690a
|
| 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 7, 2026.
Transparency logRelease files / aimio_py-0.4.1-cp315-cp315-win_amd64.whl
| Download URL | aimio_py-0.4.1-cp315-cp315-win_amd64.whl |
|---|---|
| Size | 337.2 kB |
| Tags | CPython 3.15 Windows x86-64 |
|
SHA-256 checksum How to use checksums |
7b609dc13b124acf70b55fb7ec14762a3cc867f3525ff86adc249a217fd4b206
|
|
BLAKE2b-256 checksum How to use checksums |
bc6fad2117b4992f32ff759705a40d2f5f2028c88e928671febaa47637ef7f60
|
| 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 7, 2026.
Transparency logRelease files / aimio_py-0.4.1-cp315-cp315-manylinux_2_24_x86_64.manylinux_2_28_x86_64.whl
| Download URL | aimio_py-0.4.1-cp315-cp315-manylinux_2_24_x86_64.manylinux_2_28_x86_64.whl |
|---|---|
| Size | 1.7 MB |
| Tags | CPython 3.15 Linux glibc 2.24+ x86-64 Linux glibc 2.28+ x86-64 |
|
SHA-256 checksum How to use checksums |
5e50667e14e40fb311658b7d40fd35f03a2d6bb38004c5510c4a0d752ed6c0a6
|
|
BLAKE2b-256 checksum How to use checksums |
0a4d1504428ef2d61fb289833116e19ed1a18234c023f537af5ae39b1f981fc6
|
| 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 7, 2026.
Transparency logRelease files / aimio_py-0.4.1-cp315-cp315-macosx_11_0_arm64.whl
| Download URL | aimio_py-0.4.1-cp315-cp315-macosx_11_0_arm64.whl |
|---|---|
| Size | 143.7 kB |
| Tags | CPython 3.15 macOS 11.0+ ARM64 |
|
SHA-256 checksum How to use checksums |
eca837f47a0d21caecb46491ba37a3fa3c868eaa65c012583a234a3779d25630
|
|
BLAKE2b-256 checksum How to use checksums |
6dfa3cce961e35fcd04dd73b93299aaf1648b736a9f4156527df94186f636cd8
|
| 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 7, 2026.
Transparency logRelease files / aimio_py-0.4.1-cp315-cp315-macosx_10_15_x86_64.whl
| Download URL | aimio_py-0.4.1-cp315-cp315-macosx_10_15_x86_64.whl |
|---|---|
| Size | 149.8 kB |
| Tags | CPython 3.15 macOS 10.15+ x86-64 |
|
SHA-256 checksum How to use checksums |
a4565667aa8ff4c4f36c3f6e4d4e25022c7394e49c1c3d089b85b2415addb440
|
|
BLAKE2b-256 checksum How to use checksums |
2b16a7191790f602fdf4aa585b8f564735fc4835e03232aa4ce1096c43a7ba8b
|
| 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 7, 2026.
Transparency logRelease files / aimio_py-0.4.1-cp314-cp314-win_amd64.whl
| Download URL | aimio_py-0.4.1-cp314-cp314-win_amd64.whl |
|---|---|
| Size | 337.2 kB |
| Tags | CPython 3.14 Windows x86-64 |
|
SHA-256 checksum How to use checksums |
9187ceb2e45ff0e4a2f51ad7f6cc7e94f4a5ca4592bc02c0a09b957b60b2342c
|
|
BLAKE2b-256 checksum How to use checksums |
0355ebc9e2a386989fed29fbcc9362f34d5d682c9168b8700b68f68f148aab0f
|
| 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 7, 2026.
Transparency logRelease files / aimio_py-0.4.1-cp314-cp314-manylinux_2_24_x86_64.manylinux_2_28_x86_64.whl
| Download URL | aimio_py-0.4.1-cp314-cp314-manylinux_2_24_x86_64.manylinux_2_28_x86_64.whl |
|---|---|
| Size | 1.7 MB |
| Tags | CPython 3.14 Linux glibc 2.24+ x86-64 Linux glibc 2.28+ x86-64 |
|
SHA-256 checksum How to use checksums |
0874ba43521bd7ea35de708dd5881f9e0f2d9eb97b167161cff5047b50b5df75
|
|
BLAKE2b-256 checksum How to use checksums |
331d9cdf967df4d4f8b77a79615366d9a90288e9c98f8a07d9021619c70796b4
|
| 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 7, 2026.
Transparency logRelease files / aimio_py-0.4.1-cp314-cp314-macosx_11_0_arm64.whl
| Download URL | aimio_py-0.4.1-cp314-cp314-macosx_11_0_arm64.whl |
|---|---|
| Size | 143.6 kB |
| Tags | CPython 3.14 macOS 11.0+ ARM64 |
|
SHA-256 checksum How to use checksums |
1c234f97005ae7b2ece5974b255361c110df2ca32d48957e51e40f06dd78e12d
|
|
BLAKE2b-256 checksum How to use checksums |
ebc5c8829b5516f43325dc2d6c9fe66503e9e07015e29f2c09189b6742f76d59
|
| 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 7, 2026.
Transparency logRelease files / aimio_py-0.4.1-cp314-cp314-macosx_10_15_x86_64.whl
| Download URL | aimio_py-0.4.1-cp314-cp314-macosx_10_15_x86_64.whl |
|---|---|
| Size | 149.8 kB |
| Tags | CPython 3.14 macOS 10.15+ x86-64 |
|
SHA-256 checksum How to use checksums |
d126373b00dd91dd83e30004ff09dade37c7229f8f0883bb9cffd5fe88dfeed6
|
|
BLAKE2b-256 checksum How to use checksums |
21be745ad50fc1dd1a44f4de1f0a5aa17abe9103229b104549c193da7e78890f
|
| 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 7, 2026.
Transparency logRelease files / aimio_py-0.4.1-cp313-cp313-win_amd64.whl
| Download URL | aimio_py-0.4.1-cp313-cp313-win_amd64.whl |
|---|---|
| Size | 327.6 kB |
| Tags | CPython 3.13 Windows x86-64 |
|
SHA-256 checksum How to use checksums |
0fa12e9131af68fd8aaa623e04fb19bfab0e08774d7f618a92420111b3c00917
|
|
BLAKE2b-256 checksum How to use checksums |
a95fbbb6618b6e709a4007e6345382355354e24ea08b6aac2ffcdbb763a6e8a6
|
| 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 7, 2026.
Transparency logRelease files / aimio_py-0.4.1-cp313-cp313-manylinux_2_24_x86_64.manylinux_2_28_x86_64.whl
| Download URL | aimio_py-0.4.1-cp313-cp313-manylinux_2_24_x86_64.manylinux_2_28_x86_64.whl |
|---|---|
| Size | 1.7 MB |
| Tags | CPython 3.13 Linux glibc 2.24+ x86-64 Linux glibc 2.28+ x86-64 |
|
SHA-256 checksum How to use checksums |
42325fb30453b019eb23eabbaa54914e83b3139046dff9931c6ba54b0d262c6c
|
|
BLAKE2b-256 checksum How to use checksums |
c4bb473e0a277b151a91d236f58712cf66d404f6a86ae764b8ed2425aa51bc2c
|
| 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 7, 2026.
Transparency logRelease files / aimio_py-0.4.1-cp313-cp313-macosx_11_0_arm64.whl
| Download URL | aimio_py-0.4.1-cp313-cp313-macosx_11_0_arm64.whl |
|---|---|
| Size | 143.5 kB |
| Tags | CPython 3.13 macOS 11.0+ ARM64 |
|
SHA-256 checksum How to use checksums |
0746646cb05093e20d8c88b4c010092bbee033bff0c5446da681169575b212d0
|
|
BLAKE2b-256 checksum How to use checksums |
b19482601276fe29f98df7156db336183134c14ad3b1d0d9f0f71d17801b8cce
|
| 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 7, 2026.
Transparency logRelease files / aimio_py-0.4.1-cp313-cp313-macosx_10_13_x86_64.whl
| Download URL | aimio_py-0.4.1-cp313-cp313-macosx_10_13_x86_64.whl |
|---|---|
| Size | 149.8 kB |
| Tags | CPython 3.13 macOS 10.13+ x86-64 |
|
SHA-256 checksum How to use checksums |
1173063629b2cd6cc64c426a4801766ff3ab3f6286eb816bd4db2235a027ba84
|
|
BLAKE2b-256 checksum How to use checksums |
635ba9a83bfa0d81e2e4f328768ee235781be2a21d12d1f121382569b5bb9f92
|
| 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 7, 2026.
Transparency logRelease files / aimio_py-0.4.1-cp312-cp312-win_amd64.whl
| Download URL | aimio_py-0.4.1-cp312-cp312-win_amd64.whl |
|---|---|
| Size | 327.6 kB |
| Tags | CPython 3.12 Windows x86-64 |
|
SHA-256 checksum How to use checksums |
ae2fff9b82397ab5bee049c1ac82d9a9630d0062eceed815d062c16cf285fb33
|
|
BLAKE2b-256 checksum How to use checksums |
f4fb6e2b6531095af86268d3bed0dafefaa200d427106411582aa1a05a1f5d57
|
| 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 7, 2026.
Transparency logRelease files / aimio_py-0.4.1-cp312-cp312-manylinux_2_24_x86_64.manylinux_2_28_x86_64.whl
| Download URL | aimio_py-0.4.1-cp312-cp312-manylinux_2_24_x86_64.manylinux_2_28_x86_64.whl |
|---|---|
| Size | 1.7 MB |
| Tags | CPython 3.12 Linux glibc 2.24+ x86-64 Linux glibc 2.28+ x86-64 |
|
SHA-256 checksum How to use checksums |
034b64d1edf415d470a68e6d02f7c8de120b9adb460862fe4cc52814d3472941
|
|
BLAKE2b-256 checksum How to use checksums |
fba50f2b187a593c48fbf385d661f05fefcfa3b539ac1e455bf34288345fb6fb
|
| 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 7, 2026.
Transparency logRelease files / aimio_py-0.4.1-cp312-cp312-macosx_11_0_arm64.whl
| Download URL | aimio_py-0.4.1-cp312-cp312-macosx_11_0_arm64.whl |
|---|---|
| Size | 143.4 kB |
| Tags | CPython 3.12 macOS 11.0+ ARM64 |
|
SHA-256 checksum How to use checksums |
90c1556ad55578af2fd828e44666d4a4537f0a6837c77287d2a78ca5239ec1e4
|
|
BLAKE2b-256 checksum How to use checksums |
8dbcf363e501ae353470175ee6c809f8bece2e9694a19377ba5745c9e00001ba
|
| 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 7, 2026.
Transparency logRelease files / aimio_py-0.4.1-cp312-cp312-macosx_10_13_x86_64.whl
| Download URL | aimio_py-0.4.1-cp312-cp312-macosx_10_13_x86_64.whl |
|---|---|
| Size | 149.7 kB |
| Tags | CPython 3.12 macOS 10.13+ x86-64 |
|
SHA-256 checksum How to use checksums |
383e14918945380a0b44f5f42c6e08a3ab44ca3fa3fe32d63dcf536a83e3b6ab
|
|
BLAKE2b-256 checksum How to use checksums |
ed34040c5cd6b385d9a4bd7044ae3bcd3437df2b4d63e978475b8fa9557600ea
|
| 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 7, 2026.
Transparency logRelease files / aimio_py-0.4.1-cp311-cp311-win_amd64.whl
| Download URL | aimio_py-0.4.1-cp311-cp311-win_amd64.whl |
|---|---|
| Size | 324.9 kB |
| Tags | CPython 3.11 Windows x86-64 |
|
SHA-256 checksum How to use checksums |
818abb0f69177b925d943ebec8ada262105f77ad8c43f0a018308c641d6931c0
|
|
BLAKE2b-256 checksum How to use checksums |
370b1766bbb0b1570d9e16c35112c15b4b0cb6015afa7c88397029e291cd740d
|
| 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 7, 2026.
Transparency logRelease files / aimio_py-0.4.1-cp311-cp311-manylinux_2_24_x86_64.manylinux_2_28_x86_64.whl
| Download URL | aimio_py-0.4.1-cp311-cp311-manylinux_2_24_x86_64.manylinux_2_28_x86_64.whl |
|---|---|
| Size | 1.7 MB |
| Tags | CPython 3.11 Linux glibc 2.24+ x86-64 Linux glibc 2.28+ x86-64 |
|
SHA-256 checksum How to use checksums |
e6916bbe5791a53e69cfa056ab5a579c8c6217fda74e1bc6119b56f003ded8bb
|
|
BLAKE2b-256 checksum How to use checksums |
65cef90aa221f9ce8f29f76dddd85cb7813ced65abf17b58c2691a8407d68289
|
| 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 7, 2026.
Transparency logRelease files / aimio_py-0.4.1-cp311-cp311-macosx_11_0_arm64.whl
| Download URL | aimio_py-0.4.1-cp311-cp311-macosx_11_0_arm64.whl |
|---|---|
| Size | 141.6 kB |
| Tags | CPython 3.11 macOS 11.0+ ARM64 |
|
SHA-256 checksum How to use checksums |
6ff1472ae534f1a66613feedbde05ff1a32d90732a432150b84e247f180e1a9b
|
|
BLAKE2b-256 checksum How to use checksums |
3bfc4d955ede27b4e754fa6ee69f01a1003bcab9d6b7f550df9ed2700031edaf
|
| 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 7, 2026.
Transparency logRelease files / aimio_py-0.4.1-cp311-cp311-macosx_10_9_x86_64.whl
| Download URL | aimio_py-0.4.1-cp311-cp311-macosx_10_9_x86_64.whl |
|---|---|
| Size | 147.5 kB |
| Tags | CPython 3.11 macOS 10.9+ x86-64 |
|
SHA-256 checksum How to use checksums |
2c8b12fa2f38dca266b02de0a7d519d825183ec06f34bb9028dac27adf6e095b
|
|
BLAKE2b-256 checksum How to use checksums |
7c5d5395a5496c2fe571773fd5c32f12ea4293b876d21e26a4ee04e6baed0544
|
| 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 7, 2026.
Transparency logRelease files / aimio_py-0.4.1-cp310-cp310-win_amd64.whl
| Download URL | aimio_py-0.4.1-cp310-cp310-win_amd64.whl |
|---|---|
| Size | 324.2 kB |
| Tags | CPython 3.10 Windows x86-64 |
|
SHA-256 checksum How to use checksums |
7056a91fcc1daab5a01b6d3debc98133bdade7b30b9a79d34550c8cf4552889a
|
|
BLAKE2b-256 checksum How to use checksums |
2b3eb6c4735afcb57b3a98a4f907d2c9a68d1342c05e58ae5993315304afaed5
|
| 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 7, 2026.
Transparency logRelease files / aimio_py-0.4.1-cp310-cp310-manylinux_2_24_x86_64.manylinux_2_28_x86_64.whl
| Download URL | aimio_py-0.4.1-cp310-cp310-manylinux_2_24_x86_64.manylinux_2_28_x86_64.whl |
|---|---|
| Size | 1.7 MB |
| Tags | CPython 3.10 Linux glibc 2.24+ x86-64 Linux glibc 2.28+ x86-64 |
|
SHA-256 checksum How to use checksums |
b483f36af4420d217b6883e7d4a994fb0a5a1e044283763728aa73d67797dcf8
|
|
BLAKE2b-256 checksum How to use checksums |
856ba77a9771c870f0f463ebaaf47e3d2dc5c277a913499ad06923abded33135
|
| 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 7, 2026.
Transparency logRelease files / aimio_py-0.4.1-cp310-cp310-macosx_11_0_arm64.whl
| Download URL | aimio_py-0.4.1-cp310-cp310-macosx_11_0_arm64.whl |
|---|---|
| Size | 140.6 kB |
| Tags | CPython 3.10 macOS 11.0+ ARM64 |
|
SHA-256 checksum How to use checksums |
dba5c3517f1689e52b96bb1bbedb2dba8c8058d867a15d8695aeddb3140e8442
|
|
BLAKE2b-256 checksum How to use checksums |
1b51c47449d2e34de366087b3024535435816caa95925a2d63493007dadae1ec
|
| 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 7, 2026.
Transparency logRelease files / aimio_py-0.4.1-cp310-cp310-macosx_10_9_x86_64.whl
| Download URL | aimio_py-0.4.1-cp310-cp310-macosx_10_9_x86_64.whl |
|---|---|
| Size | 146.2 kB |
| Tags | CPython 3.10 macOS 10.9+ x86-64 |
|
SHA-256 checksum How to use checksums |
dfd7a95da5363d9e8a167dedcc4558fbcddd922286203875449444e8714429c2
|
|
BLAKE2b-256 checksum How to use checksums |
77359b047c800a76ee2c8d8bd61c3110a920b8ac22482d7613fb3679436b7561
|
| 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 7, 2026.
Transparency log