GEOMETRY, NOT CERTIFICATION
Three different questions.
One wall to test.
Eye detection distance, gaze directions needed by the wall, and angular tile separation are separate constraints. This offline planner computes geometry only—it cannot tell whether a tracker will select a screen correctly.
WALL FRONT · PHYSICAL PLANE AT z = D
Screen layout & visibility
Visibility means each point lies inside the opening from every eye position in the entered rectangle. Tile-selection decision boundaries are physical screen-cell midlines projected onto the wall, not angular bisectors or a tracker SDK mapping.
PLAN VIEW · TOP
Eye, camera & aperture
Eye movement rectangle, camera position, aperture plane and extreme opening sightlines are drawn separately.
ELEVATION · SIDE
Vertical sightlines
The camera supports eye detection at zcamera; gaze rays continue to wall targets at zwall.
DISTANCE TRADE-OFF · GEOMETRY ONLY
What changes as the wall moves?
A farther wall increases physical width for a fixed assumed angle, but fixed physical tiles subtend smaller angles. The aperture and optional envelope are geometric bounds, never vendor-supported wall sizes. Camera depth and desktop reference distance stay fixed.
TRACKER SOURCE & SPECIFICATION
—
Open manufacturer/source page ↗MODEL BOUNDARIES
What these diagrams omit
- Flat centered wall/opening; no depth movement, opening thickness, lenses, occlusion or installation survey.
- Head-box dimensions apply only on the aligned 0.65 m reference plane; otherwise not extrapolated.
- Angular error bands are separable yaw/elevation at the nominal eye, not a 3D spherical cone or measured distribution.
- Aperture “fully visible” tests the whole physical screen from every modeled eye location; classification margins use physical wall-cell midlines projected as rays.
- No calibration, gaze SDK, actual visitor data, confidence, latency, bystanders or tracking-loss behavior is modeled.