Yashveer Singh
Connect
Labs · Vision Systems

Teaching machines to see the thing that matters.

Computer vision is one of the most useful layers a system can have. The lab's work here is split between practical image processing for shipped surfaces and groundwork for the upcoming robotics direction.

OpenCVWorking with
Light, fastModels
Edge devicesTargets
Small modelsBias

Why vision is a load-bearing layer.

Vision is the cheapest way for a system to perceive the world. Cameras are ubiquitous. The math has matured. The models that run them have gotten small enough to fit on edge devices. The combination makes vision one of the highest-leverage layers a modern system can ship with.

The lab's interest is specifically in the systems vision enables, not in vision for its own sake. Object recognition that triggers a workflow. Document parsing that turns paper into data. Spatial awareness for robotics. Every experiment in this folder is in service of a system, not a paper.

What I am working on today.

Practical image processing in the lab's web products. Thumbnail generation pipelines, image classification for tagging, OCR for documents that schools still hand to the system on paper. Useful, narrow, well-tested.

Adjacent learning on small vision models, especially the ones that fit on the same kind of consumer hardware the AI experiments folder is targeting. The thesis is the same. Small models, run locally, beat large models that are too expensive to call.

  • Light image processing pipelines on shipped surfaces
  • OCR for document-heavy school workflows
  • Small classifier experiments on consumer hardware
  • Spatial primitives for the upcoming robotics work

The robotics bridge.

Vision is half of what a robot needs. The other half is action. Building the vision layer ahead of the robotics builds means the robotics work, when it lands, is not starting from scratch. The folder is intentionally one of the older ones, because the dependency goes through it.

Specifically, the work here is on perception primitives: detect, classify, track, estimate distance. The robotics folder will use these as a substrate.

Build the perception layer before you need it. The robot will be cheaper that way.

What the lab will not do here.

Generic computer vision tutorials. They exist already, in better form, from people who specialize in them. The lab's contribution will be specific systems that prove the value of vision in a real workflow, not introductory material that anyone can find on YouTube.

Surveillance work. The lab is not going to build vision systems that point at people without their consent. The rule is non-negotiable, regardless of who asks.

Where this folder is heading.

Each experiment will get its own deep-dive in the blog as it earns one. The first real public surface that benefits from a non-trivial vision pipeline will live on Projects. The first robotics build that depends on this work will live on Robotics. The folder grows in service of the rest of the lab.

Where to go next.

FAQ

Questions worth answering