
Introducing LiveReview: World's First Generally Available Risk-Aware Code Review System
Auto Approve 40-50% of Your Low-Risk PRs, Safely
Tag archive

Auto Approve 40-50% of Your Low-Risk PRs, Safely
Five types of sensing in one ceiling-mounted 60 GHz mmWave radar: headcount and position, falls, respiration, sleep, and room entry and exit, reported over Wi-Fi.
A fall alert has three states - delivered, seen, answered - and only two of them can be observed. What to design for once the message has already reached the phone.
Step five of the fall alarm chain is yours to build. Why the fallback layer should be SMS and a placed call rather than push, what each channel actually guarantees, and what neither can solve.
Sleep staging on a contactless radar went from hand-tuned thresholds to learned models. Here is what that migration actually improved, and the part of the problem it does not touch.
Channel count sets the virtual aperture, and therefore angular resolution and combining gain. It does not set range resolution or displacement sensitivity — and past a point, more channels cost frame duration.
A datasheet gives you a beam angle and a mounting height. Working out how much floor the radar actually covers — and why the beam footprint and the quoted detection range disagree.
Range comes from round-trip time, velocity from the Doppler shift. The two equations, worked out for 24 GHz and 61-62.5 GHz modules, and which parameters the datasheets publish.
The sleep and fall radars fetch firmware from a URL you give them, over the same MQTT connection the telemetry uses. No vendor cloud, no account — and a few things the protocol leaves to you.
Two fields in a mmWave radar's MQTT output — online and heartBeat — look like the same health check and are not. One proves the link; the other proves the sensor. And neither supports a timeout.
A mmWave radar publishes every few seconds. Storing all of it is easy; keeping the right part of it for the right length of time is what makes historical data useful instead of expensive.
Deploying more than one 60GHz radar: the two identifiers that get confused, how to keep ClientIDs from colliding, where room identity actually lives, and a commissioning order that works.