Factory pDigger · Research

One frame in. Scene data out.

Two camera frames from a working production cell, each taken apart in seven stages. Orbit them and switch layers: surfaces and depth, the worker as measured points, a skeleton and a body model, and every stone by kind — with the holes between them.

Loading the scene…

Stage 01 of 07

Frame

It starts with a single frame from one ordinary camera — no stereo rig, no depth sensor, no second view. We don’t publish the photo: what you see is where each pixel lands.

Scene package

What’s in the scene package

Each sample ships as a small scene package: three binary layers and one description, which is all this page loads.

Depth
One relative depth value per point, stored as 16 bits: about 1 at the work surface, smaller towards the camera. A ratio, not millimetres.
Surfaces
The direction each point’s surface faces.
Labels
What each point is: the tray, one of the stones (numbered at random, as reviewed: every visible stone, none on the base plate), the worker’s body, the left or the right hand, a hole — or no data, where sample B’s frame was rotated upright and its corners stayed empty.
Description
The generic camera that lifts the points into 3D and how to decode each layer; the fitted tray surface that levels the base; one size per stone kind, and for every stone its kind, layer, footprint and centre; the holes; the worker’s skeleton — every joint’s position and whether it was measured on the visible body or inferred from the fitted rig — with its bones and the body model’s capsules; counts; honesty flags; and a SHA-256 hash for every file.
Simplified
Real frames from a working production cell, cropped to the work area and downsampled ×2; a generic camera instead of the real calibration; relative scale, not millimetres. Hidden surfaces are never invented; hidden joints come from the fitted body rig and are marked.
Left out
The photo, the camera’s real calibration, names, timestamps and the pipeline’s model identifiers. People appear only as geometry.