01 Local-first IES simulation
A local-first IES lighting simulator for the browser: import real photometry, model a room, aim your luminaires, or just describe the space — and read the work plane as a heatmap with engineering metrics. Direct light plus up to four diffuse bounces, calculated on your machine.
No account for the finder Free account for the full tool No project uploads
01 What it does
Photometry, geometry and result stay visible and editable. No hidden defaults, no black-box solver.
Drop in an LM-63 Type C file. The parser reads the angle tables, symmetry and candela, draws a polar distribution, and surfaces the lumens, watts and maximum candela behind it.
Set a rectangular room, work-plane height and surface reflectances. Place luminaires by hand, or stamp a block of them with grid placement, then tune mounting height, aim, tilt and dimming in the inspector.
Switch between total, direct and reflected illuminance. Track average, minimum, maximum and uniformity, check a target-lux threshold, and hover the grid for a point reading. Up to three labelled isolux contours trace the levels that matter, and a maintenance factor turns as-new figures into the maintained values you specify against.
Type the room and the light you want — "20 × 15 m office, 500 lx" — and LuxLab builds the scene, sizes the layout by simulation and reports the result. With a project open, ask why the result looks the way it does or request a small change; LuxLab applies it, recalculates and shows before and after. The provider reads the brief or project summary; geometry, photometry and every lux value stay in the engine. Administrators choose DeepSeek or OpenCode Go and manage the encrypted key in Settings; each person can still hide the bar in their own browser. Select several lights to move them together, and export the whole study as a PDF plan, 3D view and results report.
02 How it works
A short loop: edit, debounce, calculate. The worker keeps the interface responsive while the grid runs.
Open the IES library and load a Type C file. LuxLab checks the header and angle tables, expands symmetry, and builds a bilinear candela sampler.
Set the room and work plane, then place luminaires in plan. Use the inspector for mounting height, aim, tilt and dimming. The 3D view is read-only.
Recompute and read the false-colour map. Compare total, direct and reflected views, then check the metrics and the target threshold.
03 Local-first
No project uploads and no server-side render. An account gates the tool; the geometry, photometry and results stay in the tab. If you use Ask LuxLab, the sentence and a list of fixture names go to the configured AI provider; turning the assistant off in Settings sends nothing. Projects and IES source text live in IndexedDB, and the service worker keeps the tool available offline. Close the lid and the room is still there.
No project uploads and no tracking cookies. Your project stays browser state, not a server record; page views are counted anonymously. The assistant is the one network feature, and it is opt-out.
The engine runs in a Web Worker. Edits debounce for 360 ms; only the latest calculation survives.
An installable PWA. The app shell and fonts are precached after one visit; a cold start still checks your session online.
Exports are self-contained .luxlab.json files with every referenced IES profile embedded.
04 The plan
v0.21.0 is tagged and in use. Undo and Redo now cover the whole project: a light move, a delete, a setting change and an assistant edit are each one step, and a drag undoes as a whole. The public handbook lives at /wiki/, and the workspace has a Help menu, a shortcut sheet and a status bar that names the current tool and calculation state. Deleting a room asks first and tells you how many lights go with it. Draw a room with a rectangle drag or an orthogonal outline, edit corners and walls with snapping, type exact wall lengths and move a room with its lights. The Projects lobby remains an OrbitX portfolio. Press Select in the luminaire list to choose lights explicitly, then move or delete them together. Export a full A4 PDF with a 2D plan of every room, a 3D view, all results and the schedules. Describe a space in the Ask bar and LuxLab builds, solves and calculates it; with a project open, ask why the result looks the way it does or request a small edit, with Undo behind it.
The goal
Make a credible IES illumination study as quick as opening a tab: fast enough to iterate, private enough for client work, and accessible enough that photometry isn't locked inside desktop software.
No dates. Scope follows what the method can support honestly.
05 Method
Parse, interpolate, integrate, display. Every result is reproducible from the inputs, in the browser.
Type C, TILT=NONE, header variants and symmetry expansion. Unsupported photometry is rejected, not approximated.
Vertical and horizontal interpolation with 360° wrap-around. Dimming and the maintenance factor scale candela linearly, per luminaire.
The pure engine runs off the main thread. Edits debounce for 360 ms and the latest request wins.
The inferno scale is driven by the data's min and max. No random dithering, no per-frame noise.
Projects and IES source text persist in the browser. Exports embed every referenced profile.
The app shell, fonts and lazy 3D chunk are precached after the first visit. No CDN in the path.
Calculation
E = I(γ, C) · cos ε / r²
Up to four bounces
Bᵢ¹ = ρᵢ · Eᵢ
Bᵢk+1 = ρᵢ · Σⱼ Bⱼk Aⱼ cos θⱼ cos θᵢ / (π rᵢⱼ²)
Eref(p) = Σₖ Σᵢ Bᵢk Aᵢ cos θᵢ cos θₚ / (π rᵢ²)
Maintained
Em = MF · (Ed + Eref), MF = LLMF · LSF · LMF · RSMF
Bilinear candela in γ and C. One bounce by default and up to four; still an estimate, not a full radiosity solve.
Fixture check
750 lm declared 748 lm integrated
A public Cooper Lighting MRZ Type C profile was integrated at 1°. The check exercises angle handling and flux integration — it is not a certification.
Third-party fixture Not a compliance claim
06 Changelog
Generated from the project changelog on every deploy, so the page cannot fall behind the release.
/find/chat/. One message with the room size and the kind of light (6 × 4 m lounge, warm and cosy) is parsed locally, three OrbitX candidates are compared and the best fitting is placed in a plan of the room with the real heatmap, fitting count, average maintained lux, evenness, coverage and running cost. Follow-ups such as brighter, 6 × 5 m, cheaper to run, panels or why this one? recalculate or answer from the result. The chat reads the message in the browser and does not call the AI provider; it uses the same catalogue, engine, assumptions and consent-gated lead endpoint as the wizard. The step-by-step finder at /find/ is unchanged and remains the AI-guided path./find/chat/ without caching the chat shell.npm run smoke:advisor:chat covers the chat flow (missing size, calculation, follow-up, question, lead and outdoor refusal)./progress/ is now a short, light reading page: a one-sentence headline, three expandable product rows (live products first), what is next, the latest release and a simpler feedback form. The detailed features, limits and release notes sit behind simple disclosures instead of filling the page. The live check and the private feedback flow are unchanged.origin/pro/macos, the build now fetches it, so the progress page gets the phase detail without reinstalling /usr/local/bin/luxlab-update first. The fallback copy is also clearer when the branch cannot be read./progress/. One plain-language page covers the three LuxLab products: the Mac app (Pro) in development, the simple client website (LuxLab Match) and the full web tool. It shows what is live, what is being built, what is next, the shared engine and the honest limits. It is generated from the repository's release records rather than being hand-edited.origin/pro/macos, reads the phase checkboxes and the latest Pro version/date, and injects a safe summary into the page. Nothing from the Pro plan's strategy, pricing or competitive notes is published, and the Pro branch is not merged.LUXLAB_FEEDBACK_EMAIL.GET /api/health now includes the version and build time from a RELEASE.json written by the deploy script, so the progress page can show the version that is actually running.main has not changed, and installs the Caddy route for /progress/.GET /api/health no longer reports dev for the deployed version.07 Ready when you are
One click from the project list: 6 × 4 × 3 m, six 2,400 lm downlights, 373 lx maintained at the default 0.80 factor. A free account keeps it yours; nothing you draw is uploaded.