← Back to Projects

leptons1618@anishgiri.dev:~/projects/daystorm cat project.toml

AI / ML 2026 Active development

Daystorm

Daystorm fuses camera, CAN bus, radar, and cabin audio onto a causal 2 Hz grid so a language model answers grounded questions about a two-second driving window.

category
AI / ML
year
2026
status
Active development
stack
6 tools
highlights
5
write-up
6 min read

01Highlights

  1. Camera, CAN, radar, and audio are resampled into 16 tokens for a frozen pretrained language model.
  2. The gate requires fused exact accuracy of at least 0.90 while shuffled-sensor controls remain at or below 0.50.
  3. Causal hold and per-channel staleness budgets prevent future samples from influencing answers.
  4. Validity bits distinguish dead sensors from true zero readings, and every HTTP response reports input coverage.
  5. A fresh-hardware rerun reproduced all seven verdicts, fused exact accuracy, and peak VRAM within 0.01 GB.

02Built with

  • 01Python
  • 02PyTorch
  • 03Hugging Face Transformers
  • 04FastAPI
  • 05QLoRA
  • 06Docker

03Case study

September 4, 2026 6 min read 1,319 words

Building a Four-Modality Driving-Scene Copilot on a T4 GPU

How we fused camera, CAN bus, radar, and cabin audio into a 2 Hz event grid and a frozen vision-language model to answer grounded driving questions.

The problem

Aligning four asynchronous sensor streams with different sample rates and dropouts while preserving causality and running on a free-tier T4 GPU that lacks bfloat16 support and has limited VRAM.

The solution

We grafted new modality encoders and a fusion layer onto a frozen 3B vision-language backbone, resampled all streams onto a causal 2 Hz event grid with validity bits, and used QLoRA with fp16 and torch.compile to keep the trainable surface under 6M parameters.

Outcomes

  • The full model achieved 1.00 manoeuvre accuracy and 0.225 numeric MAE on a held-out split with zero hallucination.
  • Removing the CAN bus increased numeric MAE by 0.44 (to 0.663) and raised hallucination to 20.8%, showing the telemetry path is critical for grounding.
  • Fusion latency on a T4 measured 2.557 ms p50 with torch.compile in fp16, while decode consumed 98.5% of end-to-end time.

+1 more in the write-up

Inside the write-up

  1. Design choices
  2. Training pipeline
  3. Evaluation
  4. Resource cost
  5. Open questions and next steps
Read the full case study →