<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Trajectory Modeling | Yonghui Liu</title><link>https://lyh360121.github.io/tags/trajectory-modeling/</link><atom:link href="https://lyh360121.github.io/tags/trajectory-modeling/index.xml" rel="self" type="application/rss+xml"/><description>Trajectory Modeling</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>Trajectory Modeling</title><link>https://lyh360121.github.io/tags/trajectory-modeling/</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><item><title>Trajectory Observation–Reconstruction Co-Design</title><link>https://lyh360121.github.io/projects/trajectory-reconstruction/</link><pubDate>Sun, 08 Mar 2026 00:00:00 +0000</pubDate><guid>https://lyh360121.github.io/projects/trajectory-reconstruction/</guid><description>&lt;h2 id="research-focus"&gt;Research Focus&lt;/h2&gt;
&lt;p&gt;Urban mobility applications use discrete observations to represent continuous movement. Storage and communication constraints limit the observations that can be retained or reported. Which observations are available, and how they are reconstructed, jointly determine the movement information a system can provide.&lt;/p&gt;
&lt;p&gt;My doctoral research, &lt;em&gt;Compression–Reconstruction Co-Design for Urban Mobility Trajectories&lt;/em&gt;, studies this relationship. The aim is to preserve useful movement information at the resource level a system actually achieves, by considering observation decisions and reconstruction together.&lt;/p&gt;
&lt;h2 id="complementary-research-settings"&gt;Complementary Research Settings&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Completed-trajectory retention:&lt;/strong&gt; Once a trip is recorded, which observations should be kept under a fixed retained-point budget? Current work examines reconstruction-aware selection and refinement of retained point sets.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Live trajectory reporting:&lt;/strong&gt; As a trip unfolds, when should a source report a new observation so that a receiver can maintain an accurate movement state? Current work coordinates reporting decisions with the state propagated at the receiver.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Sparse-trajectory reconstruction:&lt;/strong&gt; How does recoverability change as gaps between available observations grow? This work studies road-consistent reconstruction and the computational cost of recovering long trajectories.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;Completed retention can use the full recorded trip; live reporting makes decisions with information available at the current time. These settings share a co-design perspective and are evaluated under their respective information conditions.&lt;/p&gt;
&lt;p&gt;Road-network structure and semantics provide another source of information for mobility models. Related work on
develops road representations and compatible labels, and examines the value of this context in stated transportation tasks.&lt;/p&gt;
&lt;h2 id="published-studies"&gt;Published Studies&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Reconstruction capability:&lt;/strong&gt;
reconstructs long trajectories from sparse, noisy GPS observations using progressive skeleton generation and parallel chunk completion. It studies the accuracy and efficiency of recovery across increasing observation intervals. Published in &lt;em&gt;Communications in Transportation Research&lt;/em&gt;.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Conditional information value:&lt;/strong&gt;
uses controlled input gating to examine the contributions of historical trajectory, current state, and available goal information to forecasting. It is a supporting information-value study within the wider research program. Published in &lt;em&gt;Knowledge-Based Systems&lt;/em&gt;.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Urban context:&lt;/strong&gt;
and
study road representations and semantic compatibility across datasets. Published in &lt;em&gt;IEEE ITSC 2025&lt;/em&gt;.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="from-research-to-systems"&gt;From Research to Systems&lt;/h2&gt;
&lt;p&gt;
is a working local prototype for inspecting GPS reporting decisions, receiver estimates, and historical retention. Its recorded-trajectory replay and explicit source–receiver states make the effects of observation decisions visible. The current prototype uses heuristic reporting, Kalman estimation, and a geometric historical baseline; it provides a setting for future evaluation of learned methods.&lt;/p&gt;
&lt;p&gt;Across these studies, the shared question is how much useful movement information a reduced observation record can support. Retained-point count and reporting ratio are evaluated alongside movement fidelity, with their resource definitions made explicit.&lt;/p&gt;</description></item><item><title>Sequential decomposition and attribution for trajectory forecasting</title><link>https://lyh360121.github.io/publications/2025-liu-sda/</link><pubDate>Tue, 23 Dec 2025 00:00:00 +0000</pubDate><guid>https://lyh360121.github.io/publications/2025-liu-sda/</guid><description>&lt;p&gt;Trajectory forecasting models keep getting longer input windows on the assumption that more history means better predictions. In practice that assumption often breaks down: accuracy gains taper off quickly, extra history adds compute cost, and longer windows pull in more noise. SDA is not another forecasting model — it is an evaluation protocol for measuring &lt;em&gt;why&lt;/em&gt; a model performs the way it does.&lt;/p&gt;
&lt;p&gt;SDA splits any trajectory forecasting input into three interpretable streams and gates them on/off in controlled combinations to measure each one&amp;rsquo;s standalone value, its marginal contribution on top of the others, and how the streams interact:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Past&lt;/strong&gt; — the historical trajectory before the current step&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Current&lt;/strong&gt; — the most recent observed state&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Prior&lt;/strong&gt; — an optional destination or goal, when available&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;Running this protocol on two real-world datasets (Porto taxi, ETH pedestrian) with both an LSTM and a Transformer backbone gives a consistent picture:&lt;/p&gt;
&lt;p&gt;
&lt;figure id="figure-accuracy-sensitivity-to-history-length-l-across-horizons-h-and-both-backbones"&gt;
&lt;div class="flex justify-center "&gt;
&lt;div class="w-full" &gt;
&lt;img alt="History-length ablation on the Porto taxi dataset: absolute error (ADE, left) and improvement over the no-history baseline (Δ%, right) for LSTM (top) and Transformer (bottom) backbones, across prediction horizons H. Accuracy gains saturate around L*≈6 (LSTM) and L*≈8 (Transformer) — feeding in more history beyond that yields almost no further improvement."
srcset="https://lyh360121.github.io/publications/2025-liu-sda/result_1_hu_f44db202d6011113.webp 320w, https://lyh360121.github.io/publications/2025-liu-sda/result_1_hu_6393443a2b4898b4.webp 480w, https://lyh360121.github.io/publications/2025-liu-sda/result_1_hu_c4f7cc914729e88a.webp 760w"
sizes="(max-width: 480px) 100vw, (max-width: 768px) 90vw, (max-width: 1024px) 80vw, 760px"
src="https://lyh360121.github.io/publications/2025-liu-sda/result_1_hu_f44db202d6011113.webp"
width="760"
height="511"
loading="lazy" data-zoomable /&gt;&lt;/div&gt;
&lt;/div&gt;&lt;figcaption&gt;
Accuracy sensitivity to history length L, across horizons H and both backbones.
&lt;/figcaption&gt;&lt;/figure&gt;
&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Accuracy gains from history &lt;strong&gt;saturate after a short window&lt;/strong&gt; (L*≈6–8 steps) regardless of backbone or prediction horizon.&lt;/li&gt;
&lt;li&gt;The &lt;strong&gt;Current&lt;/strong&gt; state alone is already highly informative at short horizons.&lt;/li&gt;
&lt;li&gt;A reliable &lt;strong&gt;Prior&lt;/strong&gt; (goal/destination) gives a bigger boost than piling on more history, especially at longer horizons.&lt;/li&gt;
&lt;li&gt;Past, Current, and Prior show &lt;strong&gt;conditional complementarity&lt;/strong&gt; — their combined value is not simply additive.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;The takeaway for model design: prioritize making good use of the latest state and any available goal information, rather than defaulting to ever-longer observation windows.&lt;/p&gt;</description></item><item><title>Enhanced trajectory reconstruction from sparse and noisy GPS data: A progressive chunked transformer approach</title><link>https://lyh360121.github.io/publications/2025-liu-enhanced-trajectory-reconstruction/</link><pubDate>Mon, 01 Dec 2025 00:00:00 +0000</pubDate><guid>https://lyh360121.github.io/publications/2025-liu-enhanced-trajectory-reconstruction/</guid><description>&lt;p&gt;GPS traces collected in the wild are sparse and noisy — long gaps between fixes are the norm, not the exception. Reconstructing a coherent, road-consistent trajectory from such data matters for mobility analysis, transportation planning, and navigation, but the long output sequences involved make it computationally expensive, and autoregressive models tend to accumulate error step by step over a long reconstruction.&lt;/p&gt;
&lt;p&gt;ProChunkFormer tackles this with a two-phase, divide-and-conquer strategy instead of decoding the full trajectory one point at a time:&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;&lt;strong&gt;Phase 1 — Skeleton generation.&lt;/strong&gt; The sparse, low-frequency GPS input and the road network are encoded and decoded into an intermediate, semi-high-frequency &amp;ldquo;skeleton&amp;rdquo; of the trajectory (&lt;code&gt;MM-Semi&lt;/code&gt;) that already follows the road network.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Phase 2 — Trajectory completion.&lt;/strong&gt; Conditioned on that skeleton — and optionally on a heuristic shortest-path estimate (&lt;code&gt;Heuristic&lt;/code&gt;) computed between each pair of consecutive skeleton points — the remaining trajectory is divided into chunks and reconstructed &lt;strong&gt;in parallel&lt;/strong&gt; with self-attention, rather than autoregressively. Concatenating all the reconstructed chunks gives the final, complete trajectory (&lt;code&gt;MM-Full&lt;/code&gt;).&lt;/li&gt;
&lt;/ol&gt;
&lt;p&gt;Self-attention is quadratic in the length of the sequence it looks at, but standard autoregressive decoding still ends up cubic in the length of the whole trajectory, because each of its output steps has to attend over an ever-growing context. ProChunkFormer avoids this by sizing each attention pass to a chunk rather than the full trajectory and generating chunks in parallel; the paper&amp;rsquo;s complexity analysis shows this cuts decoding time by roughly the cube of the number of chunks used, compared with standard autoregressive decoding. On an open-source taxi trajectory dataset, this lets ProChunkFormer match the accuracy of autoregressive transformer baselines while running faster — 13.9%, 16.5%, and 20.7% faster at sampling intervals of 60, 120, and 240 seconds, respectively — with the largest accuracy gains showing up on the hardest cases: long sampling intervals of up to 240 seconds, where it improves accuracy by 23.1%, F1 score by 18.6%, mean absolute error by 22.3%, and road-network error by 25.1% over a standard transformer baseline.&lt;/p&gt;
&lt;p&gt;
&lt;figure id="figure-ground-truth-versus-reconstructed-gps-points-for-the-same-trip-the-standard-transformers-points-collapse-together-in-the-circled-area-while-prochunkformer--which-reconstructs-the-trajectory-in-independent-parallel-chunks--keeps-them-spread-out-along-the-real-route-map-data--openstreetmap-contributors-licensed-under-cc-by-sa-20"&gt;
&lt;div class="flex justify-center "&gt;
&lt;div class="w-full" &gt;
&lt;img alt="Three side-by-side street maps comparing a reconstructed taxi trip: (a) the ground-truth route as a continuous line, (b) points reconstructed by a standard autoregressive transformer, several of which are wrongly bunched on top of each other in one spot, and (c) points reconstructed by ProChunkFormer, generated in two independent chunks (Block 1 and Block 2) and correctly spread out along the true route."
srcset="https://lyh360121.github.io/publications/2025-liu-enhanced-trajectory-reconstruction/fig-reconstruction-comparison_hu_dce41fbdb5bd8e20.webp 320w, https://lyh360121.github.io/publications/2025-liu-enhanced-trajectory-reconstruction/fig-reconstruction-comparison_hu_48ac1475c57f639b.webp 480w, https://lyh360121.github.io/publications/2025-liu-enhanced-trajectory-reconstruction/fig-reconstruction-comparison_hu_bc9e738f40e105f8.webp 760w"
sizes="(max-width: 480px) 100vw, (max-width: 768px) 90vw, (max-width: 1024px) 80vw, 760px"
src="https://lyh360121.github.io/publications/2025-liu-enhanced-trajectory-reconstruction/fig-reconstruction-comparison_hu_dce41fbdb5bd8e20.webp"
width="760"
height="478"
loading="lazy" data-zoomable /&gt;&lt;/div&gt;
&lt;/div&gt;&lt;figcaption&gt;
Ground truth versus reconstructed GPS points for the same trip: the standard transformer&amp;rsquo;s points collapse together in the circled area, while ProChunkFormer — which reconstructs the trajectory in independent, parallel chunks — keeps them spread out along the real route. Map data © OpenStreetMap contributors, licensed under CC BY-SA 2.0.
&lt;/figcaption&gt;&lt;/figure&gt;
&lt;/p&gt;
&lt;p&gt;Adding heuristic guidance — using the shortest path between consecutive skeleton points to help condition each chunk&amp;rsquo;s reconstruction — speeds up convergence during training and improves accuracy and error metrics in most configurations, though the paper reports a few cases (for example, accuracy at a 120-second sampling interval) where it produces a small decline instead.&lt;/p&gt;</description></item></channel></rss>