Skip to main content

Visin Fusion

A Python library for semantic segmentation from camera images and projected LiDAR. Five research model families share one call: model(rgb, lidar) returns class logits shaped [batch, classes, height, width].

Install

python -m pip install visin-fusion

From a source checkout instead: git clone https://github.com/visin-platform/visin-fusion.git, then python -m pip install -e . in it.

The install provides the models and the training and evaluation pipeline. Add .[visin] for Visin reporting and datasets, or .[dev] for tests. See the installation and API guide for details.

Use a model

import torch
from visin_fusion.models import CLFTv2

model = CLFTv2(num_classes=4, mode="cross_fusion", pretrained=False).eval()
rgb = torch.randn(1, 3, 256, 256)
lidar = torch.randn(1, 3, 256, 256)  # camera-aligned LiDAR projection
with torch.inference_mode():
    logits = model(rgb, lidar)  # [1, 4, 256, 256]
Model Main difference
CLFT Global ViT features fused during decoding
CLFTv2 Hierarchical Swin fusion pyramid
MaskFormerFusion Class-labelled mask queries
Mask2FormerFusion Multi-scale masked-attention queries
DeepLabV3+ Two convolutional branches with late fusion

Each model page links its research papers. See model comparison for the fusion points and Python API for modes, training and checkpoints. The LiDAR input is a three-channel projected image, not a raw point cloud.

Optional pipeline

For ZOD, Waymo, and Iseauto datasets, follow Download and train: install, download, and run the pipeline with CLI commands.

Train, test, visualize and benchmark CLFTv2 on the included sample dataset (the getting started page also shows how to use your own data):

visin-fusion quickstart

The pipeline guide covers configs, Docker, SLURM and individual stages. Add .[visin] and a Visin pipeline key to report runs; see the Visin integration guide. To rank checkpoints on a written-down protocol, see ranking on a suite.

Tests

python -m pip install -e '.[visin,dev]'
pytest tests/unit
python tools/coverage.py  # unit + end-to-end; requires >90% package coverage

See tests/README.md for focused end-to-end commands. The full documentation is at visin-platform.github.io/visin-fusion.

License

MIT.

Metadata

Release files for visin-fusion 0.5.0

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for visin-fusion 0.5.0
File Size Uploaded
visin_fusion-0.5.0.tar.gz 3.2 MB Details

Built distribution (wheel)

Table of built distributions (wheels) for visin-fusion 0.5.0
File Interpreter ABI Platform
visin_fusion-0.5.0-py3-none-any.whl Python 3 none any Details

Total release size: 6.5 MB

Release files / visin_fusion-0.5.0.tar.gz

Download URL visin_fusion-0.5.0.tar.gz
Size 3.2 MB
Tags Source
SHA-256 checksum
How to use checksums
894ec8811f24a9e5426152b992371a272d8b679700d7ea2b1cb2859cf5485891
BLAKE2b-256 checksum
How to use checksums
96120c08d5864b3bf006784088fddc347318170fe4de24ac33a21358f3063969
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.14

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 Oct 4, 2026.

Transparency log

Release files / visin_fusion-0.5.0-py3-none-any.whl

Download URL visin_fusion-0.5.0-py3-none-any.whl
Size 3.3 MB
Tags Python 3
SHA-256 checksum
How to use checksums
0459a2866870a9489293a38ff37e44c53c445c8ebc6f6771a8ca94731de2fee0
BLAKE2b-256 checksum
How to use checksums
12e9489670e5dabff63a8e9406d984ed75bd449b1b85988244cb23de4f7d1b0f
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.14

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 Oct 4, 2026.

Transparency log

Release history Release notifications | RSS feed

0.7.0

2 release files

0.6.0

2 release files

This release

0.5.0 This release

2 release files

0.4.0

2 release files

0.3.0

2 release files

0.2.0

2 release files

0.1.1

2 release files

0.1.0

2 release files

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page