Live status · Read the latest
monad-knowledge Wi-Fi sensing lab · FIIT STU
Capture corpus

Dataset coverage

What you have recorded, where, and how much is decoded.

Snapshot updated

Reset

Measurements only · Bench, console and quarantined sessions excluded. All totals and views below use these filters.

Recorded session-hours
≥ 2.0
Decoded session-hours
≥ 2.0
Days with captures
12026-10-23 → 2026-10-23
Devices / channels
1 / 13 sessions

Hours sum session durations across devices; simultaneous captures add together. Days use session start dates in Europe/Bratislava. Decoded means every segment has frame rows; it does not certify usable CSI or current reductions. 2 sessions have unknown duration.

Timeline data by device and start day
The interactive timeline uses these same daily totals. Hours sum session durations; they do not imply continuous coverage.
DeviceStart dateRecorded hDecoded h
monad022026-10-232.02.0

Dates

DatesDevicesRecorded hDecoded hSessions
2026-10-23monad022.02.03

Channels

ChannelsDevicesRecorded hDecoded hSessions
5 GHz · ch 48monad022.02.03

Devices

DevicesDevicesRecorded hDecoded hSessions
monad02monad022.02.03

Capture profiles

Capture profilesDevicesRecorded hDecoded hSessions
explore-lib-ref-day-ammonad02——1
explore-lib-ref-nightmonad022.02.01
walk-abba-48-nightmonad02——1

Sessions

3 sessions, newest first. At most 300 shown; coverage totals include every matching session.
CaptureDeviceBand / channelHoursDecode
explore-lib-ref-nightmonad025 GHz / 482.0decoded
explore-lib-ref-day-ammonad025 GHz / 48—decoded
walk-abba-48-nightmonad025 GHz / 48—decoded
Snapshot, definitions & data access

This page covers sessions listed in the lake snapshot, 407112 (2026-10-26T18:58+00:00). It cannot show captures absent from that snapshot. Channel and band are session metadata, not a per-channel dwell-time measurement. Missing durations appear as a dash; known durations still contribute to the totals.

Archive inventory: 7472 sessions, 609 quarantined and 2371 infrastructure. A claim is a card that names the session id, or whose declared capture profiles and window reach it, read from the vault when the snapshot was built. Sessions the lake already attributes carry that as a third source. Infrastructure profiles (console, smoke, benches, anything under two minutes) can never be claimed and are counted apart, never as unclaimed.

Quote useful_yield: (records − empty records) ÷ frames the radio saw. capture_yield counts an all-zero record as delivered. A low capture_yield on 2.4 GHz is DSSS/CCK traffic that yields no channel estimate, not a quiet channel. Both are derived ratios from two independent counters and exceed 1.0 on some sessions; the counts are exact, the ratios are not.

JSON: day ledger · profile census · sessions. Open a session for yields, record classes and ownership.

More toolbox instruments

In plain words Filter the recorded dataset by date, channel, device or capture profile. Compare recorded and decoded session-hours, then open the captures behind a total.