How hypothete/unstructured-lumigraph works
Project type and purpose
• This is a client-side WebGL “single-page” application that implements the “Unstructured Lumigraph Rendering” algorithm in the browser.
• Purpose: load a multi-view dataset (images + camera poses + proxy mesh), build a Three.js scene, and synthesize novel views by blending camera rays with custom GLSL shaders.
File structure
• Top level
• index.html – entry point
• app.js – main application logic
• styles.css – minimal CSS
• vertex.glsl / fragment.glsl – custom GLSL shader programs
• vendor/ – third-party libs (Three.js, shader utilities)
• data/ – four sample datasets (cube, kettle, statue, TV) each with images.txt, cameras.txt, images/, proxy geometry
• package.json – dev scripts (yarn start spins up a static HTTP server)
• Patterns
• Single‐Page App: all assets are static, served over HTTP
• Modular code in app.js: Data loader → Scene builder → Renderer → UI controls
• Shaders separate GPU logic (vertex + fragment) from JS orchestration
Key insights from README
• A static server (e.g. via yarn start) serves HTML, JS, shaders, data.
• User interaction: mouse + keyboard drive a camera controller.
• Datasets follow a uniform folder structure, and app.js contains hooks to parse cameras.txt and images.txt.
Main components & interactions
A. Static HTTP Server
• Serves index.html, app.js, CSS, GLSL files, vendor libs, dataset files
B. Client (Browser)
1. Loader Module (in app.js)
– Fetches datasets: cameras.txt, images.txt, proxy.obj, image textures
2. Scene Graph (Three.js)
– Builds mesh (proxy geometry), texture materials, camera frustums
3. Renderer (Three.js + WebGL)
– Compiles vertex.glsl & fragment.glsl into GPU shader programs
4. UI Controller
– Listens for mouse & keyboard, updates Three.js camera parameters
C. GPU Shader Programs
• Vertex Shader: transforms proxy mesh
• Fragment Shader: samples multiple camera textures, computes lumigraph blending
D. Data Store (Filesystem)
• data/<dataset>/{images.txt, cameras.txt, images/, proxy.obj}
E. External Dependencies
• Three.js (in vendor/)
• GLSL utilities (bubble sort, fovBlend code)
Architectural patterns & design principles
• Modular separation:
• Data layer (static files + loader)
• Logic layer (app.js modules: DataLoader, SceneBuilder, Renderer, InputHandler)
• Presentation layer (WebGL/GLSL shaders)
• Single‐page, event‐driven render loop pattern
• Dependency injection of dataset name via URL query param
• Reuse of Three.js scene graph for camera & mesh management