FloodMesh Field Test Dashboard

Dashboard

Filters, mode-specific outcomes, and detailed evidence for the selected Field Test data.

0 sessions

Privacy mode: the dashboard never displays raw coordinates or stable Node IDs. Exact-coordinate ingestion remains disabled unless the server flag and client request both explicitly enable it.

Measured sessions

after current filters

All planned probes

kept separate by mode

All attempted probes

unique original SEND_ATTEMPT

Direct sessions

RF range and RSSI eligible

Passive sessions

destination ACK outcome

Server sessions

returned server ACK outcome

Direct delivery success vs GPS-derived distance

No DIRECT_NODE first-send sample has GPS-derived distance under the selected filters.

Direct delivery success vs send-time RSSI

Only DIRECT_NODE samples are plotted. Verified Wi-Fi Direct and current-Wi-Fi proxy values remain separate.

No DIRECT_NODE SEND_ATTEMPT RSSI dBm samples are available.

Direct RSSI vs GPS-derived distance

Only DIRECT_NODE SEND_ATTEMPT and RECEIVE measurements are included.

No probe has both GPS-derived distance and RSSI dBm yet.

Passive delivery success vs GPS-derived distance (every hop)

Each observed PASSIVE_NODE forward-hop leg contributes one GPS-derived distance sample. Success means that probe later returned DESTINATION_ACK_RECEIVED to the origin; unobserved failed legs cannot enter this chart.

No attempted PASSIVE_NODE probe has an observed forward-hop distance under the selected filters.

Passive delivery success vs Hop count

One attempted PASSIVE_NODE probe contributes to its configured expected-hop bin. Success requires DESTINATION_ACK_RECEIVED at the origin.

No attempted PASSIVE_NODE probe has a configured expected hop count under the selected filters.

Server round-trip outcomes

Success requires SERVER_ACK_RECEIVED back at the origin after gateway and server acceptance.

0 sessions

Attempted

0 planned

Gateway log evidence

uploaded GATEWAY_RECEIVE events

Server accepted

SERVER_ACCEPTED evidence

Server ACK returned

0 aligned with attempts

Round-trip ACK rate

N/A

95% CI N/A

ACK latency P50

N/A

origin send to returned server ACK

ACK latency P95

N/A

0 final failures

Server ACK route analytics

Mesh handoffs are configured origin-to-gateway edges: 0 is a self gateway, 1 is a direct gateway, and 2+ traverses relay nodes. Session route distance is the sum of each forward hop's median GPS-derived distance across one pinned, stationary origin-to-gateway route; it excludes the internet leg and returned ACK path.

Handoff coverage N/A (0/0 attempts) Eligible session routes 0/0 Session-distance attempt coverage N/A (0/0 attempts) Latency + handoffs 0/0 successful ACKs Latency + session distance 0/0 successful ACKs

Server ACK success vs mesh handoffs

Every attempted SERVER_ROUND_TRIP probe with configured expected_hops contributes to the denominator.

No attempted SERVER_ROUND_TRIP probe has a configured handoff count under the selected filters.

Server ACK success vs session route distance

All attempts, including failures, enter the denominator when their pinned stationary session has eligible route geometry.

No SERVER_ROUND_TRIP session has stable median GPS distance evidence for every expected hop under the selected filters.

Per-message server ACK latency vs session route distance

Each point is one successful SERVER_ROUND_TRIP message with end-to-end origin-send to returned-ACK latency and its eligible pinned-session route distance.

No successful SERVER_ROUND_TRIP probe has the required latency and eligible session-route distance evidence.

Per-message server ACK latency vs mesh handoffs

Each point is one successful SERVER_ROUND_TRIP message. Horizontal jitter separates overlapping messages but does not change their configured handoff value.

No successful SERVER_ROUND_TRIP probe has the required latency and configured handoff evidence.

Server ACK sessions

Public-source and self-gateway runs are listed separately with their gateway and final returned ACK evidence.

0 measured

Session	Date	Source to gateway	Route	Session route distance	App version	Attempted	Gateway evidence	Server accepted	ACK at source	Success	Log coverage
No SERVER_ROUND_TRIP session matches the selected filters.

All rates use unique session + sequence pairs. Direct RF plots contain DIRECT_NODE sessions only. Passive success requires DESTINATION_ACK_RECEIVED; server success requires SERVER_ACK_RECEIVED at the origin. Duplicate uploads and retries do not increase denominators.

FloodMesh Field Test

Settings

Clear Field Test Logs