A camera bridge, a browser-based vision workbench, an inspection runtime, and an operator console cover different parts of the same industrial vision workflow. This repository pins reviewed revisions of all four components and documents how they exchange video, camera information, and runtime results.
The components remain independent projects with their own history, setup, validation notes, and limitations. This repository connects them through Git submodules; it is not a monorepo or a complete deployable system.
The workbench and console are both frontend applications, but they serve different tasks. The workbench is used to inspect streams and tune a predefined OpenCV.js pipeline. The console connects to the runtime API for session control, configuration, and result review. It does not depend on the workbench.
| Component | Role | Boundary |
|---|---|---|
lucid-livekit-bridge |
Publishes Lucid camera or MP4 frames to LiveKit and provides camera discovery and parameter APIs | Source acquisition and streaming |
industrial-vision-workbench |
Provides browser-side OpenCV.js controls, ROI tools, presets, and synthetic-stream testing | Image-processing and parameter exploration |
wafer-runtime-reference |
Manages inspection sessions, runtime state, result records, and report-facing APIs | Inspection runtime |
industrial-vision-console |
Displays live streams, runtime diagnostics, configuration, and inspection history | Operation and result review |
git clone --recurse-submodules https://github.com/RocketWill/industrial-vision-system-reference.git
cd industrial-vision-system-referenceFor an existing clone:
git submodule update --init --recursiveEach submodule stays at a specific reviewed commit. Component updates are recorded explicitly instead of following remote branches automatically.
The relevant starting point depends on the part of the workflow being examined:
- Camera discovery, frame publication, or LiveKit rooms: start with
lucid-livekit-bridge. - Browser-side filters, ROI interaction, presets, or camera controls: start with
industrial-vision-workbench. - Session state, inspection processing, result storage, or report export: start with
wafer-runtime-reference. - Live operation, configuration, or result review: start with
industrial-vision-console.
The component boundaries note describes the shared contracts and integration order in more detail.
There is no one-command launcher in this repository. LiveKit, token services, camera drivers, infrastructure definitions, and production configuration remain outside its scope. Setup commands, ports, environment variables, and current validation status are documented by the component that owns them.
Public examples use browser-generated visuals, generic camera frames, or simulated wafer runs. They show that interface and integration paths were exercised; they do not establish defect accuracy, process capability, production readiness, or customer deployment status. Customer data, production media, credentials, device identifiers, and recipes are not included.
The four components are curated public snapshots of engineering work developed in 2026. Their histories remain separate so each project can be reviewed on its own. This repository fixes the reviewed revisions in one place and adds the context needed to read them together.
This repository is published for technical reference. No license is granted for reuse, redistribution, or commercial deployment.
Third-party components retain their own licenses. Review the notices and dependency metadata inside each submodule.
Will Cheng · GitHub