DinkyDeaks

I built BenchReport for the step after a VNA export: comparing several Touchstone measurements, applying a frequency-bounded acceptance limit and producing something another engineer can review.

The free browser edition overlays up to three S1P/S2P files, lets you select a golden reference, identifies the exact sampled frequency behind a failure and produces a printable report. File contents stay in the browser. Three synthetic filter measurements are built in, so the complete workflow can be tried without an upload or account.

I have also just published v0.4.0 with the guided demo, parser tests and RF-specific guides. I am looking for feedback on difficult-but-valid Touchstone structures and information missing from the report. Please use only synthetic or non-sensitive examples.

Try it: https://edwarddeakin06-maker.git...

One of the main design constraints behind BenchReport was keeping Touchstone measurement contents off an application server. The browser reads selected S1P/S2P files with the File API, then parsing, complex-value conversion, plotting, limit evaluation and report generation happen client-side.

The privacy claim is deliberately narrow: the site itself is hosted normally and aggregate analytics can record a page visit, but the contents of selected measurement files are not uploaded to BenchReport. The built-in filter demo is synthetic, so the complete workflow can be evaluated without supplying any data.

The current parser supports common Touchstone 1.0-style S1P/S2P files in DB/angle, magnitude/angle and real/imaginary representations. It rejects malformed rows and evaluates limits only at samples actually present in the file there is no hidden interpolation at band boundaries.

If you work with RF measurement data, I would value feedback on what evidence a generated report needs to be genuinely reviewable. Guided demo: https://edwarddeakin06-maker.git...