RADAR FUSION
v2 · TASF engine
Radars
—
Tracks
—
Alerts
—
Engine
—C++ TASF · WASM
--:--:--
CONNECTING

v1 vs v2 — what is different

Aspectv1 · radar-fusionv2 · this app
Fusion coreTypeScript EKF + Hungarian GNN (in-house)C++17 Tracking_And_Sensor_Fusion (EKF + greedy GNN), compiled to WASM
AssociationGlobal assignment (Hungarian) per sensor batchGreedy nearest neighbour per measurement, scan mutex per sensor
GatingMahalanobis χ² 3-DoF (99.5 %)Mahalanobis χ² 99 %: radar 4-DoF (r, az, el, vr), EO 2-DoF
Measurement modelPolar (r, az, el)Polar + radial velocity; angle-only EO camera
Track initiationTwo-point (kinematic pairing)Single radar plot (original); 5 radar hits to confirm
LifecycleTENTATIVE → CONFIRMED → COASTING → LOST → DELETEDSame states — COASTING/LOST added to the original TENTATIVE/CONFIRMED/DEAD
Multi-sensorNativeAdded: sensor positions, per-sensor scan mutex, streaming API
Runs inBrowser worker / NodeBrowser worker / Node (WASM) and native C++ (CMake)

Both versions share the same API contract, operator UI concepts and simulation scenarios, so results are directly comparable.

Run benchmark (v2)

Scored against simulation truth after a 10 s warm-up. CLI equivalent: npx tsx scripts/benchmark.ts all 180.

Paste v1 results (JSON from v1’s benchmark)

Results

No benchmark runs yet. Run one on the left.