cuda-zarr
Two zarr-python v3 compatible stores using kvikio for remote and local data: https://docs.rapids.ai/api/kvikio/stable/quickstart/
plus (at least one) codec(s).
install
uv pip install cuda-zarr[cuda12]
usage
Nvidia's documentation on how level/checksum are used in Zstd (the only exported codec here) is quite sparse (here?), but testing seems to show levels -7 to 22 all work. This codec only seems to work when used either roundtrip i.e., data is read and written using it, or only read. If you write data with this, it seems you can't read it back in with CPU data.
from cuda_zarr import ZstdGPU, CuFileStore, RemoteCuFileStore
import zarr
zarr.registry.register_codec("zstd", ZstdGPU)
zarr.config.set({'codecs.zstd': f"{ZstdGPU.__module__}.{ZstdGPU.__name__}", "buffer": "zarr.core.buffer.gpu.Buffer", "ndbuffer": "zarr.core.buffer.gpu.NDBuffer"})
store = CuFileStore('/path/to/store')
remote_store = RemoteCuFileStore.from_url("http://my_remote_data_server.com/path/to/the/store.zarr")
...
Untested in unit testing is the RemoteCuFileStore with s3 (although http is tested). Also RemoteCuFileStore only supports get and not set via kvikio (it will go through normal CPU based fsspec io in the set case).
1 maintainer
Metadata
1 maintainer
Release files for cuda-zarr 0.1.3
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 |
|---|---|---|---|---|
| cuda_zarr-0.1.3.tar.gz | 16.5 kB | With provenance | Details for cuda_zarr-0.1.3.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| cuda_zarr-0.1.3-py3-none-any.whl | Python 3 | none | any | Details for cuda_zarr-0.1.3-py3-none-any.whl |
Total release size: 32.6 kB
Release files / cuda_zarr-0.1.3.tar.gz
| Download URL | cuda_zarr-0.1.3.tar.gz |
|---|---|
| Size | 16.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
a65324b8cc856166f393c9f6ed5234004229ae090662c616f6b4ebb57341c867
|
|
BLAKE2b-256 checksum How to use checksums |
e310d9cf2ef0cf1c22b7e523c008f3f94291ce734915af2706ede3e5a53f6291
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.12.9
|
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 Feb 25, 2025.
Transparency logRelease files / cuda_zarr-0.1.3-py3-none-any.whl
| Download URL | cuda_zarr-0.1.3-py3-none-any.whl |
|---|---|
| Size | 16.1 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
efcf34a3df0ea1c69e07cf7c112b9ef5f1da216a97caa3a78c54df223780f147
|
|
BLAKE2b-256 checksum How to use checksums |
4cedd6667a84331d83ab9feac23a7fe0204fe2b8938eb6ca47a1f1ea3b9a693d
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.12.9
|
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 Feb 25, 2025.
Transparency logSecurity for cuda-zarr 0.1.3
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.
Full provenance
All 2 files in this release have been uploaded with provenance metadata.
Attestation for cuda_zarr-0.1.3.tar.gz
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 Feb 25, 2025.
Transparency logA 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.
