VoltScope TraceLab
Inspiration
A strange waveform is not always a strange sensor. A dropped packet or restarted device clock can make a capture look more alarming than the source system. I wanted a tool that first asks whether the timeline can support the conclusion.
What it does
VoltScope TraceLab takes a sensor CSV and separates recording observations from signal observations. It preserves acquisition order, identifies missing packets and clock breaks, and presents each finding alongside its exact source rows. Engineers can review an observation, export its evidence, and reproduce the finding from the original capture.
How it works
The application runs entirely in the browser. A strict parser validates sequence IDs, two millisecond timebases and signal values. An integrity pass constructs observed segments and marks missing or unreliable samples. A transparent median/MAD baseline identifies later deviations; a separate detector exposes unchanged readings without calling them failures. SHA-256 binds exported findings to the imported capture bytes.
Distinctive contribution
The product does not stop at an anomaly chart. It carries a finding through recording-integrity assessment, source-row inspection, human assessment and reproducibility checking. It refuses to repair missing data automatically or turn a relative clock trend into a confident causal diagnosis.
Demonstration and verification
The included damaged fixture is explicitly synthetic. It produces 591 received samples, nine missing packets, three recording observations and three signal observations. The clean and relative-clock fixtures use the same analysis path. The package includes 66 passing core tests, UI checks, screenshot evidence, a presentation and a captioned continuous recording of native Chromium application interactions.
Limits and next steps
This is an engineering diagnostic prototype, not a certified detector or safety device. It has not been evaluated on field captures. Next steps are comparison against labeled real capture faults, configurable device rollover semantics and further Safari compatibility testing. It never controls equipment.
AI assistance
ChatGPT assisted with implementation, synthetic fixtures, tests, documentation and assets. Runtime analysis is deterministic JavaScript, not an AI model. No prior submitted project code was reused.
Revision and verification limits
Version 1.1.1 includes fixes verified through Windows Chromium and Playwright WebKit at real loopback URLs, with 22 native checks per product in each browser. These include original-byte exports and races between old and new input. A clean macOS Python environment passed the 200 combined regression tests and full report reproduction on 2026-09-11. Safari-specific validation remains incomplete.
Log in or sign up for Devpost to join the conversation.