e↗entertrainment
← All project stories
Research & accessibility / PROJECT STORY

DICOM Lens

Inspect layered volumes and structures in an interactive 3D research workspace.

Research module4 MIN READDEVELOPMENT ARCHIVE · OCT 2026

Choose among four genuine precomputed backend outputs: axial, narrow-window axial, coronal MPR and a 60 mm MIP. The viewer switches retained images; it does not decode DICOM in your browser. Native Lens UI capture remains outstanding.

Explore the synthetic decoder lab ↗
DICOM Lens backend · actual AssistantApp offline decoder output of a newly generated synthetic CT-number insert phantom, 18 October 2026. Axial slice, 176 × 176 pixels. No patient data; this is a backend image, not a native Lens interface screenshot.
DICOM Lens backend · actual AssistantApp offline decoder output of a newly generated synthetic CT-number insert phantom, 18 October 2026. Axial slice, 176 × 176 pixels. No patient data; this is a backend image, not a native Lens interface screenshot. Open full size ↗
Actual AssistantApp DICOM coronal reformat of the synthetic phantom, 880 × 360 pixels. Six known HU classes and voxel counts matched the independent generator. This is a bounded pipeline check, not clinical validation or a segmentation demonstration.
Actual AssistantApp DICOM coronal reformat of the synthetic phantom, 880 × 360 pixels. Six known HU classes and voxel counts matched the independent generator. This is a bounded pipeline check, not clinical validation or a segmentation demonstration. Open full size ↗
PROJECT REVIEW · 18 October 2026

Inside the project

Prepared with the project’s development agent from source and retained evidence. This is a project-owner assessment, not an independent customer review. Dated checks were not rerun for this website.

The Lens is the 3D stage of the NeuroAtlas DICOM workstation. A study's segmented structures sit as persistent layers you can show, shade, isolate, cut through and fly around. Since October it can do more than show anatomy: you can pick a structure and pull it out to examine it enlarged and turned. You can call it 'this' and ask the built-in assistant about it; the assistant answers only what the scan supports, such as a Hounsfield-unit profile on calibrated CT, and refuses the rest with a reason. You can also isolate or cut it by voice or gesture. Vessel bifurcations found by the vessel analysis appear as markers you can see through the vessel wall. A displaced or enlarged copy is display-only: every measurement stays in the scan's own millimetres. It is a research and engineering tool, explicitly non-diagnostic, and it runs offline on macOS.

The 18 October 2026 website demonstration uses actual outputs from the AssistantApp offline DICOM decoder on a newly generated synthetic CT phantom. The 176 × 176 × 72 volume contains six known HU values. Decoded voxel counts and means for all six classes, and the whole-volume mean, match the independently generated ground truth. The browser viewer selects retained axial, narrow-window, coronal MPR and 60 mm maximum-intensity-projection images. It does not run the decoder in the browser and does not capture the native Lens interface. This bounded engineering check uses no patient data and establishes neither segmentation performance nor clinical validity. A native Lens interaction recording remains outstanding.

What stands out

  • Persistent layer stack: re-shading changes a key, not the geometry, so toggling a structure does not re-upload its mesh
  • Display-only presentation: a structure can be popped out, enlarged and turned while picks and measurements still resolve in source-scan millimetres
  • Honest 'this': answers are scoped per question (HU profile with partial-volume share, left/right comparison) and unsupported questions are refused with the reason
  • One vocabulary for voice, assistant and gesture (isolate, cut, keep, cancel); anatomical plane names are deliberately refused rather than guessed
  • Bifurcation markers drawn through the lumen wall, verified by an actual SceneKit render

Current limits

  • Never run with a real camera, microphone or iPad: gaze and hand interaction are tested in software only
  • The gaze/hand framework is gated behind a compile flag and has not landed in the Integration branch
  • macOS only (the stage uses SceneKit and AppKit)
  • Self-tests prove behaviour, not usability: there is no recorded user session
  • Non-diagnostic; surfaces are display aids over segmentation masks

Features & evidence

Persistent 3D/4D layer stage

component-tested

Toggle, shade, decimate for display and fly through every segmented structure

Recorded evidence

Built 2026-09-05; viewer harness (real SCNView) 77/77 on 2026-10-05

Presentation transform (pop out / enlarge / turn)

component-tested

Hold a structure and move or scale a display copy; reset restores it

Recorded evidence

Picks resolve in the layer frame; harness and probe suites; combined app build green 2026-09-29 → 2026-10-05

Assistant 'this' tools

component-tested

Ask about the held, looked-at or selected structure: HU profile, water/NWU eligibility, display actions

Recorded evidence

Tools dicom_get_this / _measurement / _this_display_action; probe ThisAssistant 11/11 (2026-09-29)

Voice / gesture isolate and cut

component-tested

Push-to-talk phrases and flicks isolate, cut, keep or cancel; plane drags never enter undo; cut edits are bound to their series

Recorded evidence

Probe LensVocabulary 7/7, ObjectActions 12/12; P1 review fix 2026-09-30

Gaze / hand / head interaction (ocular spatial framework)

source

Look to focus, pinch to grab, head parallax, trial runner

Recorded evidence

Combined build with the framework green 2026-10-05; adapter harness 17/17; never camera-run; not in Integration

Vessel bifurcation markers

component-tested

Pink markers at each branch junction, listed with angles and Murray ratio

Recorded evidence

Render check: seen through an opaque wall, with an ordinary-marker control; probe 8/8 (2026-10-03)

Review updates & corrections
  • New since 17 Oct bio: look/pinch/manipulate/ask integration (Sept 29 – Oct 5), assistant 'this' tools, the voice/gesture vocabulary, and bifurcation markers
  • The bio's 'files staged, not committed' is superseded: the work is committed on branch claude/lens-dicom-full-speed at 41edc5114 and merged UNCOMMITTED into the live Main tree; it is not in Integration
  • iOS: the Lens is macOS-only; gating fixed 2026-10-05
  • The 18 October 2026 website demonstration uses actual outputs from the AssistantApp offline DICOM decoder on a newly generated synthetic CT phantom. The 176 × 176 × 72 volume contains six known HU values. Decoded voxel counts and means for all six classes, and the whole-volume mean, match the independently generated ground truth. The browser viewer selects retained axial, narrow-window, coronal MPR and 60 mm maximum-intensity-projection images. It does not run the decoder in the browser and does not capture the native Lens interface. This bounded engineering check uses no patient data and establishes neither segmentation performance nor clinical validity. A native Lens interaction recording remains outstanding.

Workflow walkthrough

A guide to the native workflow. These steps describe the app; only the recordings and images embedded on this page are available as website demonstrations.

  1. Open a contrast CT study and let segmentation finish; structures appear as layers on the Lens stage
  2. Select a structure, then pop it out to enlarge and turn it, and reset it back to anatomy
  3. Ask the assistant 'what is the HU profile of this?' and read the per-question answer and refusals
  4. Say or type 'isolate this', then 'cut it across' and 'keep the cut'
  5. Run the vessel workup and view the pink bifurcation markers through the vessel wall
Planned captures · not yet available
  • Pop out, turn and ask about 'this' on a phantom volume
  • Bifurcation markers visible through a vessel wall

Explore the connections.

Browse all project stories ↗