physical_ai_av
This repository contains a python developer kit and documentation (in the form of a wiki and interactive notebooks) for working with the NVIDIA Physical AI Autonomous Vehicles Dataset, one of the largest, most geographically diverse collections of multi-sensor data empowering AV researchers to build the next generation of Physical AI based end-to-end driving systems.
Support
📣 Usage questions and discussion about Physical AI AV dataset & devkit: please join us on the Alpamayo NV Developer Forum.
🐛 Code-level bugs, documentation issues, and feature requests: file a GitHub issue using the appropriate template (Bug report, Documentation request, or Feature request). The relevant NVIDIA responder is auto-assigned via the assignees: field on the template.
🚨 Security vulnerabilities: please use NVIDIA's Vulnerability Disclosure Program. Do not file security issues publicly here.
Installation & Setup
pip install physical_ai_av
To use this package to access the data hosted on Hugging Face, you'll need to:
- Create a Hugging Face account (if you don't have one already).
- Login and agree to the NVIDIA Autonomous Vehicle Dataset License Agreement visible at the top of the PhysicalAI AV dataset card.
- Create a User Access Token (if you don't have one already) and choose a method for authentication.
Metadata
Release files for physical_ai_av 0.2.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 | |
|---|---|---|---|---|
| physical_ai_av-0.2.3.tar.gz | 25.4 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| physical_ai_av-0.2.3-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 57.7 kB
Release files / physical_ai_av-0.2.3.tar.gz
| Download URL | physical_ai_av-0.2.3.tar.gz |
|---|---|
| Size | 25.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
bf4c8a93ca2c7f6510403b1366d80a331d077b41157a7b716ea9c84ab43c9370
|
|
BLAKE2b-256 checksum How to use checksums |
f5cbe1aa59113c6fe1f74adb2b71f18924fd86845099439895445c23605e137e
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
uv/0.13.5 {"installer":{"name":"uv","version":"0.13.5","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"Ubuntu","version":"26.04","id":"resolute","libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":true}
|
Release files / physical_ai_av-0.2.3-py3-none-any.whl
| Download URL | physical_ai_av-0.2.3-py3-none-any.whl |
|---|---|
| Size | 32.3 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
f8defcdea29acb10c45a7d7235bc805d447a6f27ba269778745099f5ed7e84fe
|
|
BLAKE2b-256 checksum How to use checksums |
49b19793a27fd46a3202778c58e51c27c1a2207f1ebb88f4e221600014fd1bc8
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
uv/0.13.5 {"installer":{"name":"uv","version":"0.13.5","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"Ubuntu","version":"26.04","id":"resolute","libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":true}
|
Security for physical_ai_av 0.2.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.
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.