mirror of
https://github.com/ruvnet/RuView
synced 2026-07-24 17:43:20 +00:00
Dragan Spiridonov
3ed43e9a2f
Three coupled defects, all found by building the wheel and running the real
suite on Apple Silicon rather than trusting green CI.
1. THE P6 SOTA BINDINGS NEVER REACHED USERS (release blocker).
`pip-release.yml`'s cibuildwheel built the DEFAULT feature set, so published
wheels contained none of aether/mat/meridian. `pip install
wifi-densepose[aether]` then raised ImportError — and the extra is empty, so
its own error message ("install the [aether] extra") sent users in a circle.
A pip extra cannot enable a Rust cargo feature on an already-built wheel, so
the only way P6 reaches PyPI is to compile it in.
Fix: the RELEASE build opts in via `MATURIN_PEP517_ARGS="--features sota"`
(per-platform, since CIBW_ENVIRONMENT_LINUX overrides CIBW_ENVIRONMENT).
`default = []` in Cargo.toml, the RuView#1387-default-wheel-budget-config
fix-marker, and the wheel-size-budget job are all left UNTOUCHED — they keep
guarding the small base compile. Measured published wheel: 1.68 MiB, well
under the ADR-117 §5.4 5 MiB budget. Proven: built via the exact PEP517 path,
`import wifi_densepose.aether/mat/meridian` all succeed.
2. THE WHEEL SMOKE TEST COULD NOT SEE #1.
CIBW_TEST_COMMAND only asserted `hello()` and PRINTED `__build_features__`.
The one signal that would reveal missing bindings was dumped to stdout and
ignored, so a featureless wheel published green. It now ASSERTS the p6
features are present and imports the three modules. Proven red→green: fails
on the old featureless wheel ("missing SOTA bindings: [...]"), passes on the
fixed one.
3. THE AETHER PARITY TESTS WERE NOT PORTABLE ACROSS THE WHEEL MATRIX.
`test_aether.py` and the native `aether_parity.rs`/`aether_weights_parity.rs`
hashed the raw f32 embedding bytes (SHA-256) against a committed golden. The
embedding is pure f32 with transcendental ops (ln/sqrt/cos) that are not
bit-reproducible across CPUs/libm, so the hash only ever matched the one arch
that generated it. This passed in python-ci (x86) but fails on the aarch64 /
macOS-arm wheels this same project ships — latent until #1 is fixed and the
bindings actually load. Every tolerance/behavioral assertion already passed;
only the two byte-hash tests failed, which is the signature of a non-portable
golden, not a logic bug.
Fix: compare to a committed golden VECTOR within tolerance
(atol=rtol=1e-4 — ~100x cross-arch f32 drift, ~100x under any real algorithm
change), on both the Python and native sides against the SAME golden. Native
≈ golden and binding ≈ golden together prove binding ≈ native, portably.
`.sha256` goldens replaced by `.json` vectors.
Also: the aether/mat/meridian import shims told users to `pip install
wifi-densepose[<x>]` on a missing feature — an empty extra that cannot help.
Corrected to name the real fix (rebuild with `--features <x>`); message tests
updated to assert the honest message and forbid the misleading one.
Verified on aarch64/macOS: full `python/tests/` suite 227 passed against a wheel
built with the new mechanism; `cargo check --tests --features aether` clean.
The native `.rs` parity tests were converted by inspection and cargo-checked but
not executed — they link against the PyO3 crate and no workflow runs them today
(a pre-existing gap; wiring `cd python && cargo test --features sota` into
python-ci would make the native anchor actually run).
Co-Authored-By: Ruflo & AQE
61 lines
2.3 KiB
Python
61 lines
2.3 KiB
Python
"""MAT — Mass Casualty Assessment Tool (ADR-024 crate, ADR-185 P3).
|
|
|
|
WiFi-based disaster-survivor detection and START-protocol triage from CSI:
|
|
ingest CSI frames, run a scan cycle, and query detected survivors by triage.
|
|
|
|
Included in the official ``wifi-densepose`` wheels. It is absent only from a
|
|
from-source build that did not enable the Rust ``mat`` feature; rebuild with
|
|
``maturin ... --features mat`` (or ``--features sota``) in that case.
|
|
|
|
Quick start::
|
|
|
|
from wifi_densepose.mat import DisasterConfig, DisasterResponse, DisasterType, ScanZone
|
|
|
|
cfg = DisasterConfig(DisasterType.Earthquake, sensitivity=0.9, confidence_threshold=0.1)
|
|
resp = DisasterResponse(cfg)
|
|
resp.initialize_event(0.0, 0.0, "Building A") # required before scanning
|
|
resp.add_zone(ScanZone.rectangle("North Wing", 0.0, 0.0, 50.0, 30.0))
|
|
for amp, phase in csi_stream:
|
|
resp.push_csi_data(amp, phase)
|
|
resp.scan_once() # one detection cycle
|
|
for s in resp.survivors():
|
|
print(s.id, s.triage_status, s.confidence, s.location)
|
|
|
|
Honest scope (ADR-185 §3.4): the ADR's Rust-side `scan_once()` wrapper was
|
|
unnecessary — this binding drives one cycle of the public async
|
|
`start_scanning()` (with `continuous_monitoring` forced off) on an internal
|
|
runtime. `initialize_event` + `add_zone` are required before `scan_once`.
|
|
`Survivor.latest_vitals` returns the latest reading (the Rust accessor is a
|
|
history). The detection pipeline is real but unvalidated on live rubble.
|
|
"""
|
|
|
|
from __future__ import annotations
|
|
|
|
from wifi_densepose import _native
|
|
|
|
# MAT symbols are compiled into `_native` only under the Rust `mat` feature.
|
|
if not hasattr(_native, "DisasterResponse"):
|
|
raise ImportError(
|
|
"wifi_densepose.mat is not available in this build. The official "
|
|
"wheels include it; if you built from source, rebuild with "
|
|
"`maturin ... --features mat` (or `--features sota`)."
|
|
)
|
|
|
|
DisasterType = _native.DisasterType
|
|
TriageStatus = _native.TriageStatus
|
|
DisasterConfig = _native.DisasterConfig
|
|
DisasterResponse = _native.DisasterResponse
|
|
ScanZone = _native.ScanZone
|
|
Survivor = _native.Survivor
|
|
VitalSignsReading = _native.VitalSignsReading
|
|
|
|
__all__ = [
|
|
"DisasterType",
|
|
"TriageStatus",
|
|
"DisasterConfig",
|
|
"DisasterResponse",
|
|
"ScanZone",
|
|
"Survivor",
|
|
"VitalSignsReading",
|
|
]
|