---
pretty_name: "MAAP3D Patched Dependency Wheels"
license: other
license_name: multiple-upstream-licenses
license_link: "https://huggingface.co/datasets/MAAP3D/dependency-wheels/blob/main/LICENSE"
tags:
  - computer-vision
  - maap3d
  - python
  - wheels
---

# MAAP3D patched dependency wheels

This is a versioned artifact repository, not a dataset or a Python package
index. It publishes pinned downstream wheels used to beta-test specific
MAAP3D deployment profiles. These artifacts are not official releases of the
upstream projects.

The wheels contain third-party code and retain their applicable upstream
licenses. They are **not** relicensed under MAAP3D's AGPL license. See
[`LICENSE`](LICENSE), the individual files under [`licenses/`](licenses/),
and [`THIRD_PARTY_WHEEL_NOTICES.zip`](THIRD_PARTY_WHEEL_NOTICES.zip) before
redistributing or using an artifact.

## Published artifacts

| Distribution | Downstream version | Intended MAAP3D profile | License |
| --- | --- | --- | --- |
| `mmdet` | `3.3.0+maap3d.cfd5d3a9.1` | CUDA 12.1 and CUDA 12.8 full/dev | Apache-2.0 |
| `sam3` | `0.1.0+maap3d.847e1a3b.1` | Legacy CUDA 12.8 artifact with PyTorch >=2.7 | Custom SAM License dated November 19, 2025 |
| `sam3` | `0.1.0+maap3d.847e1a3b.2` | CUDA 12.1 and CUDA 12.8 full/dev with PyTorch >=2.4 | Custom SAM License dated November 19, 2025 |
| `chumpy` | `0.71+maap3d.580566ea.1` | MAAP3D OpenMMLab stacks, including Python 3.12 GB10 | MIT |
| `mmpose` | `1.3.2+maap3d.gb10.5408bc76.1` | GB10 `mmcv-lite` only | Apache-2.0 generally; EDPose files are identified as IDEA License 1.0 |

These are pure-Python wheels, but that does not make every artifact compatible
with every Python, PyTorch, CUDA, MMCV, or platform combination. Use each wheel
only in its stated profile. Do not install all four wheels together as a generic
environment.

## What was changed

- **MMDetection:** widens the package's runtime MMCV version guard so the
  validated MAAP3D stack can use MMCV 2.2.0, adds an inline downstream
  modification notice, and uses a downstream version. The optional `mim`
  dependency metadata retains upstream's `mmcv<2.2.0` declaration; this wheel
  is therefore not intended to be installed through the `[mim]` extra.
- **SAM3:** relaxes the `ftfy` dependency for the BoxMOT-compatible stack,
  declares an explicit PyTorch minimum, removes an incorrect MIT classifier,
  adds a modification notice, and uses a downstream version. Version `.2`
  lowers the declared minimum from PyTorch 2.7 to the validated PyTorch 2.4
  runtime without replacing the immutable `.1` artifact. The SAM License is a
  custom license with use and redistribution
  conditions; read [`licenses/sam3/LICENSE`](licenses/sam3/LICENSE) in full.
- **Chumpy:** packages the pinned upstream Python 3.12-compatible revision
  instead of patching Chumpy 0.70 in `site-packages`, and uses a downstream
  version.
- **MMPose:** omits eager EDPose and RTMO registry imports needed by unsupported
  GB10 paths and uses a downstream version. EDPose source and configuration
  files remain in the wheel; the special-file licensing recorded in
  [`licenses/mmpose_gb10/LICENSES.md`](licenses/mmpose_gb10/LICENSES.md) still
  applies. Consult that notice together with the original
  [ED-Pose license file](https://github.com/IDEA-Research/ED-Pose/blob/master/LICENSE);
  this repository does not resolve or simplify those upstream terms.

Exact upstream repositories, commits, checksums, and modification summaries
are recorded in [`PROVENANCE.json`](PROVENANCE.json).

## Installation and profile restrictions

The preferred installation path is the matching MAAP3D profile installer,
which is responsible for selecting compatible PyTorch, CUDA, MMCV, and other
dependencies. These wheels are not complete environment bundles.

- The GB10 MMPose wheel must be installed with `--no-deps` after the
  profile-specific `xtcocotools` build.
- Use SAM3 `.2` with the modern CUDA 12.1 / PyTorch 2.4 profile. The older
  `.1` wheel retains its original PyTorch >=2.7 metadata for reproducibility.
- The MMPose wheel is limited to the GB10 `mmcv-lite` profile. Its disabled
  eager registrations mean the EDPose and MMDetection-dependent RTMO paths
  are not supported in that profile.
- The MMDetection wheel changes the runtime compatibility guard only; do not
  request its optional `[mim]` extra.

For a manual download, select one artifact and pin a published tag or, for
maximum immutability, the full repository commit SHA:

```bash
hf download MAAP3D/dependency-wheels \
  FILENAME.whl \
  --repo-type dataset \
  --revision TAG_OR_FULL_COMMIT_SHA \
  --local-dir ./maap3d-wheels
```

Install the downloaded wheel only after preparing the matching profile. For
example, the GB10 MMPose artifact deliberately requires `--no-deps`:

```bash
python -m pip install --no-deps ./maap3d-wheels/mmpose-1.3.2+maap3d.gb10.5408bc76.1-py3-none-any.whl
```

## Integrity and provenance

After downloading the complete artifact set, verify it with:

```bash
sha256sum -c SHA256SUMS
```

`SHA256SUMS` covers the five wheels and
`THIRD_PARTY_WHEEL_NOTICES.zip`. It does not cover repository documentation,
the standalone license copies, or `PROVENANCE.json`.

The notices archive contains a snapshot of the release notice, provenance, and
upstream license copies. Each wheel also carries its applicable package license
metadata. Model checkpoints, PyTorch/CUDA runtimes, MMCV, `xtcocotools`, and
other transitive dependencies are not included. Model checkpoints can have
terms separate from their source code and must be obtained from an authorized
source.

## Release maintenance

Published artifacts must be treated as immutable:

1. Never replace a wheel while retaining its filename or downstream version.
2. Rebuild changed artifacts under a new downstream version.
3. Regenerate `SHA256SUMS`, `PROVENANCE.json`, and the notices archive.
4. Commit the complete set and create a new repository tag.
5. Pin automated installers to a full commit SHA when strict reproducibility is
   required; tags are convenient release labels but can technically be moved.

This repository currently contains beta-test artifacts for the MAAP3D 0.5
development line.