Files
ruvnet--RuView/docs/research/sota-2026-05-22/ticks/tick-6.md
T
ruv 2e742305ba research(R10): through-foliage wildlife sensing — physics feasibility + per-species gait taxonomy
ITU-R P.833-9 vegetation-attenuation model + ESP32-S3 link-budget
solver produce bounded sensing range estimates per frequency and
foliage density. Plus a biomechanics-grounded gait-frequency taxonomy
spanning bears (0.5 Hz) to mice (15 Hz).

Headline ranges (121 dB link budget, 10 dB SNR margin):

  freq    sparse   moderate   dense
  2.4 GHz 99.6 m   12.0 m     4.1 m
  5 GHz   19.9 m   5.2 m      2.1 m

The 2.4 GHz / sparse cell (~100 m) is the practical sweet spot —
10x camera-trap coverage, always-on rather than PIR-triggered.

Honest scope called out explicitly: this is feasibility math, not
field measurements. Animal cooperation, foliage flutter, regulatory
limits, and BSSID-fingerprint degradation in remote forest are all
real follow-up problems.

Vertical applications (10-20 year horizon) catalogued:
- Endangered-species population census
- Wildlife corridor verification
- Invasive-species early warning
- Anti-poaching (human gait well-separated from wildlife)
- Livestock-on-rangeland tracking
- Agricultural pest control

Cross-connects to:
- R5 (saliency is task-specific — per-species classifier needs own
  saliency map, same lesson as R12)
- R8 (wildlife sensing wants CSI not RSSI for per-subcarrier shape)
- R9 (fingerprint K-NN primitive transfers to per-individual ID)
- R7 (multi-link consistency for corridor coverage)

Pure-NumPy, no framework deps. ITU model + binary search solver.
Coordination: tick avoided PROGRESS.md to prevent races (horizon-
tracker M3+ track concurrent at the time).

Files:
* examples/research-sota/r10_foliage_attenuation.py
* examples/research-sota/r10_foliage_results.json
* docs/research/sota-2026-05-22/R10-through-foliage-wildlife.md
* docs/research/sota-2026-05-22/ticks/tick-6.md
2026-05-22 00:59:11 -04:00

47 lines
1.9 KiB
Markdown
Raw Blame History

This file contains ambiguous Unicode characters
This file contains Unicode characters that might be confused with other characters. If you think that this is intentional, you can safely ignore this warning. Use the Escape button to reveal them.
# Tick 6 — 2026-05-22 03:55 UTC
**Thread:** R10 (through-foliage wildlife sensing)
**Verdict:** Physics feasibility + per-species gait taxonomy + bounded range estimates.
## What shipped
- `examples/research-sota/r10_foliage_attenuation.py` — ITU-R P.833-9 vegetation attenuation model + ESP32-S3 link-budget solver + per-species gait band table.
- `examples/research-sota/r10_foliage_results.json` — full machine-readable numbers.
- `docs/research/sota-2026-05-22/R10-through-foliage-wildlife.md` — research note with range table, gait taxonomy, vertical applications, honest scope.
## Headline numbers (this tick)
**Max ESP32-S3 sensing range through foliage (121 dB link budget, 10 dB SNR margin):**
| Frequency | Sparse | Moderate | Dense |
|---|---:|---:|---:|
| 2.4 GHz | **99.6 m** | 12.0 m | 4.1 m |
| 5 GHz | 19.9 m | 5.2 m | 2.1 m |
The 2.4 GHz / sparse cell (~100 m) is the practical sweet spot — **10× the spatial coverage of a camera trap** in matched conditions, always-on rather than PIR-triggered.
**Per-species gait taxonomy** (DSP-actionable):
- 0.51.5 Hz: bear, sloth, wild boar
- 1.22.5 Hz: human walking
- 1.53.5 Hz: elk, raccoon, wolf
- 1.84.5 Hz: deer, fox
- 4.015.0 Hz: squirrel, mouse, songbird
## 10-20 year verticals catalogued
- Endangered-species population census (replaces camera traps)
- Wildlife corridor verification
- Invasive-species early warning
- Poaching detection (human gait band well-separated from wildlife)
- Livestock-on-rangeland tracking
- Agricultural pest control
## Coordination
Tick-6 used the same `ticks/tick-N.md` convention to avoid PROGRESS.md races.
## Major out-of-tick news (horizon-tracker just completed)
Horizon-tracker agent `a62cf580…` reported full M1M7 completion: 6 MCP tools, 6 CLI subcommands, ADR-104, 16 passing tests. Final summary in `HORIZON.md`. The MCP/CLI track is structurally complete; npm publish handoff is documented for the user.