6D Pose Streaming
Built around a custom Java HTTP/WebSocket server that streams live position, orientation, RMS error, latency, dropped-frame, and tracking-state data into the dashboard.
3D Tracking / Java / Three.js
TrackQA is a full-stack debugging workflow for OEM engineers integrating optical or electromagnetic 3D tracking systems. A Java backend simulates real-time 6D pose behavior, streams frames over WebSocket, and feeds a React + TypeScript dashboard that visualizes tracking state, detects integration issues, and generates engineering reports.
Built around a custom Java HTTP/WebSocket server that streams live position, orientation, RMS error, latency, dropped-frame, and tracking-state data into the dashboard.
Uses Three.js and React Three Fiber to render the tracked tool, measurement volume, target point, coordinate axes, and live path trail so integration failures are visible in context.
Combines deterministic issue detection, Gemini-powered diagnosis, CSV export, and Markdown report generation for Jira, GitHub, or Confluence handoff.
Project Notes
The backend models both optical and electromagnetic tracking behavior, including line-of-sight obstruction, dropped frames, EM distortion drift, RMS error changes, latency spikes, and measurement-volume warnings. Simulator state is configurable so each scenario can be reproduced instead of treated as a random demo artifact.
The React, TypeScript, Vite, and TailwindCSS frontend is styled as a dark-mode engineering console with live metrics, configuration controls, issue detection, calibration results, AI diagnosis, and report generation. The 3D view makes the tracked tool, target, axes, and trail easy to inspect while the numeric panels expose the system health signals.
TrackQA uses deterministic rules to classify integration problems such as LINE_OF_SIGHT_OBSTRUCTION, EM_DISTORTION, LATENCY_SPIKE, OUT_OF_VOLUME, and CALIBRATION_FAILED. This gives the dashboard predictable engineering behavior even when the AI diagnosis layer is disabled.
The Java backend includes calibration logic, in-memory session logging, and CSV export endpoints for raw tracking frames. That lets an engineer move from live observation to reproducible evidence without leaving the tool.
Gemini API integration turns tracking metrics and detected issues into a root-cause diagnosis, suggested next steps, and a Jira-style issue summary. When no Gemini API key is configured, TrackQA falls back to a local mock diagnosis so the demo stays fully functional.
Videos