01
Who it’s for
An engineer in a SAR test lab working from a large master test table.
A test lab · live
Three workbooks in. Exact, likely or needs review.
For an engineer in a SAR test lab working from a large master test table, who used to match test positions against the worst-case and hot-unit lists across separate workbooks by eye.
Runs locally in the browserPython 3 · Mac, Linux, WindowsLive · private
SAR Position Matcher
Local-first cross-referencing of test positions against worst case and hot units.
Sample workbooks
Which band sheets should this run apply to?
Not every department needs every band. Pick the sheets to match, e.g. just the LTE low bands (B5, B12, B13, B26, B71).
| Sheet | Row | Test position | Side | Channel | RB | Sample no. | WC confidence | WC position | WC dist. | Hot unit sheet | Hot frequency | Hot unit consistency |
|---|
SAR_Position_Match_Report.xlsxsample · not saved
Sample workbooks with made-up bands, positions and unit numbers, written for this page. It is a simulation of the tool’s screens and its matching rules, not the lab’s tool or data.
What it’s for
Four parts, plainly.
02
By hand, until now
They matched test positions against worst-case and hot-unit lists across separate workbooks by eye.
03
What I built
You upload the master table, the worst-case positions file and the hot units file, pick the band sheets, and it cross-references them, marking each match exact, likely or needs review. It flags conflicting hot units and exports an Excel report.
04
Where it is
Live and private: it runs locally in the browser with Python 3 on Mac, Linux or Windows.
Rough edges
Where it stops.
- One lab’s layoutsBuilt for one lab’s workbook layouts.
- No guessingAmbiguous matches are left for a person to confirm.
Honest line: “needs review” is a feature, not a failure. When the names in two files can’t be lined up with confidence, the tool says so. It is private, so there is no download or code link.