The dataset viewer is not available for this split.
Error code: StreamingRowsError
Exception: ArrowInvalid
Message: JSON parse error: Invalid value. in row 0
Traceback: Traceback (most recent call last):
File "/usr/local/lib/python3.14/site-packages/datasets/packaged_modules/json/json.py", line 324, in _generate_tables
df = pandas_read_json(f)
File "/usr/local/lib/python3.14/site-packages/datasets/packaged_modules/json/json.py", line 38, in pandas_read_json
return pd.read_json(path_or_buf, **kwargs)
~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.14/site-packages/pandas/io/json/_json.py", line 815, in read_json
return json_reader.read()
~~~~~~~~~~~~~~~~^^
File "/usr/local/lib/python3.14/site-packages/pandas/io/json/_json.py", line 1014, in read
obj = self._get_object_parser(self.data)
File "/usr/local/lib/python3.14/site-packages/pandas/io/json/_json.py", line 1040, in _get_object_parser
obj = FrameParser(json, **kwargs).parse()
File "/usr/local/lib/python3.14/site-packages/pandas/io/json/_json.py", line 1176, in parse
self._parse()
~~~~~~~~~~~^^
File "/usr/local/lib/python3.14/site-packages/pandas/io/json/_json.py", line 1392, in _parse
ujson_loads(json, precise_float=self.precise_float), dtype=None
~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
ValueError: Expected object or value
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/src/services/worker/src/worker/utils.py", line 149, in get_rows_or_raise
return get_rows(
dataset=dataset,
...<4 lines>...
column_names=column_names,
)
File "/src/libs/libcommon/src/libcommon/utils.py", line 272, in decorator
return func(*args, **kwargs)
File "/src/services/worker/src/worker/utils.py", line 129, in get_rows
rows_plus_one = list(itertools.islice(safe_iter(ds, dataset=dataset), rows_max_number + 1))
File "/src/services/worker/src/worker/utils.py", line 489, in safe_iter
yield from ds.decode(False) if ds.features else ds
File "/usr/local/lib/python3.14/site-packages/datasets/iterable_dataset.py", line 2818, in __iter__
for key, example in ex_iterable:
^^^^^^^^^^^
File "/usr/local/lib/python3.14/site-packages/datasets/iterable_dataset.py", line 2355, in __iter__
for key, pa_table in self._iter_arrow():
~~~~~~~~~~~~~~~~^^
File "/usr/local/lib/python3.14/site-packages/datasets/iterable_dataset.py", line 2380, in _iter_arrow
for key, pa_table in self.ex_iterable._iter_arrow():
~~~~~~~~~~~~~~~~~~~~~~~~~~~~^^
File "/usr/local/lib/python3.14/site-packages/datasets/iterable_dataset.py", line 536, in _iter_arrow
for key, pa_table in iterator:
^^^^^^^^
File "/usr/local/lib/python3.14/site-packages/datasets/iterable_dataset.py", line 419, in _iter_arrow
for key, pa_table in self.generate_tables_fn(**gen_kwags):
~~~~~~~~~~~~~~~~~~~~~~~^^^^^^^^^^^^^
File "/usr/local/lib/python3.14/site-packages/datasets/packaged_modules/json/json.py", line 327, in _generate_tables
raise e
File "/usr/local/lib/python3.14/site-packages/datasets/packaged_modules/json/json.py", line 290, in _generate_tables
pa_table = paj.read_json(
io.BytesIO(batch), read_options=paj.ReadOptions(block_size=block_size)
)
File "pyarrow/_json.pyx", line 342, in pyarrow._json.read_json
File "pyarrow/error.pxi", line 155, in pyarrow.lib.pyarrow_internal_check_status
File "pyarrow/error.pxi", line 92, in pyarrow.lib.check_status
raise convert_status(status)
pyarrow.lib.ArrowInvalid: JSON parse error: Invalid value. in row 0Need help to make the dataset viewer work? Make sure to review how to configure the dataset viewer, and open a discussion for direct support.
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, the individual files under licenses/,
and 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 |
CUDA 12.8 full/dev with PyTorch >=2.7; not CUDA 12.1 | 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
mimdependency metadata retains upstream'smmcv<2.2.0declaration; this wheel is therefore not intended to be installed through the[mim]extra. - SAM3: relaxes the
ftfydependency for the BoxMOT-compatible stack, declares the upstream runtime's PyTorch >=2.7 requirement, removes an incorrect MIT classifier, adds a modification notice, and uses a downstream version. The SAM License is a custom license with use and redistribution conditions; readlicenses/sam3/LICENSEin 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.mdstill applies. Consult that notice together with the original ED-Pose license file; this repository does not resolve or simplify those upstream terms.
Exact upstream repositories, commits, checksums, and modification summaries
are recorded in 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-depsafter the profile-specificxtcocotoolsbuild. - The SAM3 wheel requires PyTorch >=2.7 and must not be used in the legacy CUDA 12.1 / PyTorch 2.2.2 profile.
- The MMPose wheel is limited to the GB10
mmcv-liteprofile. 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:
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:
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:
sha256sum -c SHA256SUMS
SHA256SUMS covers the four 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:
- Never replace a wheel while retaining its filename or downstream version.
- Rebuild changed artifacts under a new downstream version.
- Regenerate
SHA256SUMS,PROVENANCE.json, and the notices archive. - Commit the complete set and create a new repository tag.
- 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.
- Downloads last month
- 4