ego-vision
Composable egocentric vision model components and pipelines for hand and camera geometry.
The initial scope is intentionally narrow: raw model wrappers plus an episode-level pipeline boundary for the best VGGT-Omega + HaWoR stack.
episodes of av.VideoFrame
-> VGGTOmegaModel
-> HaWoRHandReconstructor
YoloHandDetector + HaWoRModel + ManoLayer
-> HaWoRHandMotionInfiller
-> HandTrackingPipeline result
The egovision.models namespace contains raw model components. The
egovision.pipelines namespace owns model scheduling and hand-tracking
orchestration.
VGGT-Omega and the HaWoR inference modules needed by the pipeline live under
egovision.models, so users do not need separate research-repo checkouts or
PYTHONPATH setup. Checkpoints are still loaded from local paths or Hugging
Face.
from egovision import (
EpisodeInput,
HandTrackingConfig,
HandTrackingPipeline,
HaworReconstructionConfig,
VggtOmegaConfig,
)
pipeline = HandTrackingPipeline(
HandTrackingConfig(
hand_reconstruction=HaworReconstructionConfig(batch_size=64),
camera_pose_estimator=VggtOmegaConfig(batch_size=1),
)
)
results = pipeline.predict_episodes(
[EpisodeInput(frames=av_frames)]
)
Install
pip install ego-vision
Heavy model dependencies are optional:
pip install "ego-vision[models]"
Development
uv sync --dev
uv run pytest
uv run ruff check --force-exclude .
uv run ruff format --force-exclude --check .
uv run ty check
Local hooks use the same commands:
uv run pre-commit run --all-files
Release
Publishing is handled by GitHub Actions with PyPI trusted publishing.
To release:
- Bump
versioninpyproject.toml. - Push the commit to
main. - The
Publish packageworkflow builds the wheel and sdist, publishes to PyPI, then creates thevX.Y.Ztag and GitHub release.
The workflow can also be run manually from GitHub Actions with target
testpypi or pypi. The normal release path only needs the pypi trusted
publishing environment configured for the ego-vision project.
Metadata
Release files for ego-vision 0.1.25
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 |
|---|---|---|---|---|
| ego_vision-0.1.25.tar.gz | 123.8 kB | With provenance | Details for ego_vision-0.1.25.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| ego_vision-0.1.25-py3-none-any.whl | Python 3 | none | any | Details for ego_vision-0.1.25-py3-none-any.whl |
Total release size: 268.7 kB
Release files / ego_vision-0.1.25.tar.gz
| Download URL | ego_vision-0.1.25.tar.gz |
|---|---|
| Size | 123.8 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
5e006a4f0f298eeeced609a0c77856c06e61d8591552b7a8e6f4468c0efeae8a
|
|
BLAKE2b-256 checksum How to use checksums |
4aad1d472f1f488e6020b54d930b95197aac3dcfd9a9f0be6c32c35ab883f61c
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
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 Jun 4, 2026.
Transparency logRelease files / ego_vision-0.1.25-py3-none-any.whl
| Download URL | ego_vision-0.1.25-py3-none-any.whl |
|---|---|
| Size | 144.8 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
501363d08e441a05b62903625c3a818c2f169b17e6198a9ab33ebed0d445d981
|
|
BLAKE2b-256 checksum How to use checksums |
2d53a2ab363cd2d853cf5dfbb4848aa06cd52632f916fd827693ae20d5720e52
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
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 Jun 4, 2026.
Transparency logSecurity for ego-vision 0.1.25
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
Both files in this release have been uploaded with provenance metadata.
Attestation for ego_vision-0.1.25.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 Jun 4, 2026.
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.