Asking the fleet what it is doing…
monad-knowledge Wi-Fi sensing lab · FIIT STU
Campaign session

01KW07A8W18VV6HFZEYG02RX48

finished 2026-06-25 20:25:04.641663+00:00 → 2026-06-25 20:26:06.142090+00:00 · 9 runs · supervisor: react-agent

“Sparse-BLE-cadence axis: the naive always-anchor fusion is DOMINATED at both ends. Dense BLE (<~7s): held-BLE ~= fused ~= 0.77 (CSI adds nothing, confirms v2). Sparse BLE (>~12s): plain CSI-only (1.39, flat) beats both held-BLE (up to 2.68) and fused (up to 2.01). The fused only beats held-BLE past ~25s (CSI shape vs very-stale BLE) but never beats the BEST-of-{BLE,CSI}. Design lesson: the right architecture is a CONFIDENCE-WEIGHTED SWITCH (trust BLE while fresh, fall back to CSI when the anchor goes stale), not a blind blend. CSI's distinct value is as the stale-BLE fallback, not an always-on improvement.”

Archive snapshot, as of 18 h ago — the run corpus is rebuilt once a day, so this page is not a live reading. The fleet panel is the live one; it refreshes every 30 s.

Success criteria

CriterionResolved
Reuses the v2 matched-occupancy multi-seed coupled runs; ble device-counter + CSI features per (floor x seed). yes
fusion_cadence sweeps BLE cadence {1..80 frames}; reports CSI-only / BLE-held(ZOH) / fused MAE per cadence, 3-seed mean+/-sd. yes
Identifies the regime where CSI's between-tick shape helps: fused beats held-BLE past ~25s cadence. yes
Honest framing: the naive fusion is dominated at both ends; the result motivates a switching/confidence fusion, not a blend. yes

Synthesis

Sparse-BLE-cadence — where (if anywhere) does CSI earn its keep?

v2 found fused ~= BLE-only when BLE is dense. This axis sweeps the BLE advertising cadence (1-80 coarse frames = ~1-80 s) and compares, per cadence, three estimators against true occupancy (3 seeds x 2 target floors, source-calibrated CSI map):

  • CSI-only (no anchor): flat 1.39 persons (cadence-independent).
  • BLE-held (device-count sampled at ticks, zero-order-hold between): 0.77 at 1 s, rising to 2.68 at 80 s as the held value goes stale.
  • fused (CSI shape + BLE level): 0.77 at 1 s, rising to 2.01 at 80 s.

The naive fusion is dominated at both ends.

  • Dense BLE (<~7 s): held-BLE <= fused (0.75-0.94 vs 0.89-1.26). CSI's shape adds noise to an already-good anchor — confirms the v2 "fused ~= BLE-only".
  • Sparse BLE (>~12 s): plain CSI-only (1.39) beats both held-BLE and fused. When BLE is very stale, you are better off ignoring it and trusting the (drifted) CSI map than anchoring to a stale count.
  • fused beats held-BLE only past ~25 s (CSI's delta helps vs a very-stale anchor), but never beats the best-of-{BLE, CSI} at any cadence.

The honest lesson. CSI's distinct value is not an always-on blend improvement — it is as a fallback when the BLE anchor goes stale. The right architecture is a confidence-weighted switch: trust the BLE device-count while it is fresh (it is the better estimator at realistic cadences), and fall back to the CSI map once the anchor exceeds a staleness threshold (~10-15 s here). The always-anchor offset-hold fusion tested here carries stale-BLE error into the sparse regime and is therefore dominated. This sharpens the thesis fusion story: the modalities are complementary in time (BLE = accurate-but- intermittent absolute; CSI = continuous-but-drifting relative), and the contribution is a switching rule, not a Kalman-style constant blend.

Caveats: the CSI map here is the cross-floor transferred (drifted) map (MAE 1.39) — a per-floor- adapted CSI map would raise CSI-only's floor and shift the crossover; the BLE device-counter is modelled (p_detect+Gaussian), not measured; 3 seeds, 2 target floors, test-lab/ResPlan geometries. Next: implement

  • test the staleness-switch fusion, and a per-floor-adapted CSI map.

Criticism adversarial review

Written by the campaign-critic subagent against the brief's success criteria — read it as the counter-position to the synthesis above.

Self-critical notes

This axis was built to find CSI's distinct value and returned a qualified negative for the naive fusion: (a) the fused estimator is dominated by best-of-{BLE-held, CSI-only} at every cadence, so "fusion helps" is false as implemented; (b) the apparent fused < held-BLE crossover past ~25 s is real but uninteresting because CSI-only already beats both there; (c) the comparison uses a transferred (drifted) CSI map — a per-floor-adapted CSI map would change the crossover and is the fairer next test; (d) BLE device-counter is modelled, single sigma, 3 seeds. The constructive output is a concrete design (staleness-switch / confidence-weighted fusion) and the falsification of "always blend". The honest claim is complementary-in- time modalities, not a demonstrated fusion win.

Attached runs

Run Gate Purpose Replay
EMKR0PMJ fusion-fix-matched-multiseed replay
4S0N16XM fusion-fix-matched-multiseed replay
W8438NK6 fusion-fix-matched-multiseed replay
6A8E8KQC fusion-fix-matched-multiseed replay
1DZS3DK1 fusion-fix-matched-multiseed replay
1HK2QCM3 fusion-fix-matched-multiseed replay
2WAMKD1J fusion-fix-matched-multiseed replay
53Y631KD fusion-fix-matched-multiseed replay
1F934V2N fusion-fix-matched-multiseed replay