<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Autonomous Sensing | Yonghui Liu</title><link>https://lyh360121.github.io/tags/autonomous-sensing/</link><atom:link href="https://lyh360121.github.io/tags/autonomous-sensing/index.xml" rel="self" type="application/rss+xml"/><description>Autonomous Sensing</description><generator>HugoBlox Kit (https://hugoblox.com)</generator><language>en-us</language><lastBuildDate>Sun, 11 Oct 2026 00:00:00 +0000</lastBuildDate><image><url>https://lyh360121.github.io/media/sharing.png</url><title>Autonomous Sensing</title><link>https://lyh360121.github.io/tags/autonomous-sensing/</link></image><item><title>Autonomous Traffic Sensor Web (ATSW)</title><link>https://lyh360121.github.io/projects/autonomous-traffic-sensor-web/</link><pubDate>Sun, 11 Oct 2026 00:00:00 +0000</pubDate><guid>https://lyh360121.github.io/projects/autonomous-traffic-sensor-web/</guid><description>&lt;h2 id="overview"&gt;Overview&lt;/h2&gt;
&lt;p&gt;ATSW is a working local research prototype for exploring how GPS observation decisions affect the movement state available to a receiver. Independent sources replay recorded trajectories and decide when to report a new observation. A web workspace shows the received evidence, movement estimates, forecasts, and reporting decisions as playback advances.&lt;/p&gt;
&lt;p&gt;The prototype connects to my research on
: selecting or reporting an observation changes the information available for recovering movement. It provides an inspectable setting for studying that relationship.&lt;/p&gt;
&lt;h2 id="implemented"&gt;Implemented&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Adaptive reporting:&lt;/strong&gt; Each source compares its current GPS observation with a local replica of the receiver&amp;rsquo;s predicted state. A heuristic policy reports significant deviations and periodically refreshes the receiver. Periodic and all-observation policies provide comparison modes.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Receiver-state maintenance:&lt;/strong&gt; Constant-velocity Kalman prediction and updates, implemented with Stone Soup, maintain each receiver&amp;rsquo;s position estimate. Delivered GPS observations update the estimate; between reports, the receiver advances by prediction.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Live inspection:&lt;/strong&gt; The workspace supports playback, pause and single-step controls, per-source decision logs, forecasts, and requests for a source&amp;rsquo;s next recorded observation.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Historical comparison:&lt;/strong&gt; An elapsed recorded window can be reduced to selected original observations and reconstructed between them. This branch currently uses a geometric retention baseline and linear interpolation.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Run evidence:&lt;/strong&gt; A local journal and JSON export record received observations, estimates, and diagnostic events for inspection.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="what-the-prototype-evaluates"&gt;What the Prototype Evaluates&lt;/h2&gt;
&lt;p&gt;Replay comparisons pair position error with the ratio of delivered GPS observations. The ratio measures report count; network bytes and device energy require separate measurement. Received GPS evidence and predicted or updated state estimates remain distinct in the workspace.&lt;/p&gt;
&lt;p&gt;The live receiver uses reported observations. The History view separately accesses an elapsed source recording for retrospective retention and reconstruction comparisons. These two views examine different information conditions.&lt;/p&gt;
&lt;p&gt;Recorded sources and their independent receiver states run in one local process. The implemented version uses heuristic reporting, Kalman estimation, and geometric historical reconstruction. Its current scope is recorded GPS replay.&lt;/p&gt;
&lt;h2 id="next-steps"&gt;Next Steps&lt;/h2&gt;
&lt;p&gt;The next stage is to integrate and evaluate compatible learned reporting and recovery modules while preserving the source–receiver information boundary. Live device connections and coordination across sources are further development directions, supported by the observation and command interfaces.&lt;/p&gt;</description></item></channel></rss>