Robust OT-Guided Generative Residual Domain Adaptation for Bike-Sharing Demand Prediction under Temporal Domain Shift
This paper proposes Gen-ROTDA, a robust optimal transport-guided generative residual domain adaptation framework that effectively predicts bike-sharing demand under temporal domain shifts by transferring residual patterns and trimming high-cost transport matches, outperforming various baselines in noisy and multi-year scenarios.
Original paper licensed under CC BY 4.0 (http://creativecommons.org/licenses/by/4.0/). This is an AI-generated explanation of the paper below. It is not written or endorsed by the authors. For technical accuracy, refer to the original paper. Read full disclaimer
Imagine you are a city planner trying to guess how many people will rent bikes from a specific station at a specific hour. You have a very smart computer model trained on data from last year (2025). You want to use this model to predict demand for next year (2026).
The problem is that people change. Maybe a new office building opened, the weather patterns shifted, or commuters changed their habits. If you just use last year's model directly, it will make mistakes because the "rules" of the city have changed. This is called Temporal Domain Shift.
This paper introduces a new method called Gen-ROTDA to fix this. Here is how it works, explained through simple analogies:
1. The "Anchor" and the "Drift" (Decomposition)
Imagine the bike demand is like a boat on a river.
- The Anchor: Some things about the boat stay the same no matter the year. The station's location, the time of day, and whether it's a weekend are like the boat's anchor. These are stable. The authors build a simple model just for these stable parts.
- The Drift (Residual): The part that changes is the "drift"—the extra demand caused by new events, weird weather, or shifting habits. This is the messy, unpredictable part.
Instead of trying to predict the whole boat movement again, the authors' method only tries to predict the drift (the residual). They subtract the stable "anchor" prediction from the real data and only try to fix the messy leftover part. This makes the problem much easier.
2. The "Translator" (The Generator)
Now, imagine you have a dictionary from 2025 (Source) and you need to speak 2026 (Target). The words are slightly different.
- The paper uses a Generator (a small AI translator). It takes the 2025 "drift" data and tweaks it just enough so it looks more like 2026 data.
- Crucially, it doesn't rewrite the whole story; it just adds a little "translation layer" so the 2025 data fits better with 2026 patterns without losing the original meaning.
3. The "Smart Matchmaker" with a "Safety Net" (Robust Optimal Transport)
This is the most important part. To teach the model, you need to match 2025 data points with 2026 data points.
- Standard Matching (OT): Imagine a matchmaker trying to pair up 2025 and 2026 data points based on how similar they are.
- The Problem: Sometimes, the 2026 data has "noise"—weird records caused by a sudden storm, a data glitch, or a one-time event. A standard matchmaker might try to force a match between a normal 2025 day and a weird 2026 day, which ruins the prediction.
- The Solution (Robust OT): The authors added a Safety Net. Before finalizing the matches, the system looks at the "cost" of each match. If a match is too weird or expensive (like trying to pair a sunny day with a hurricane day), the system cuts that match and ignores it. It only keeps the "good" matches to train the model.
What Did They Find?
The authors tested this on Citi Bike data in New York City from 2021 to 2026.
- Best at the Main Task: For predicting 2026 based on 2025, their method (Gen-ROTDA) made the fewest errors compared to other methods.
- The "Safety Net" is Key: When they intentionally added "garbage" or weird data to the 2026 set (simulating bad weather or data errors), the standard methods got confused and failed. Gen-ROTDA, thanks to its "Safety Net" (Robust OT), stayed calm and accurate.
- Not a Magic Bullet: While it was the best at handling the "noisy" data and was the top method among the "Optimal Transport" family, simple methods like just "fine-tuning" (re-training the model slightly on new data) were still very strong competitors overall.
The Bottom Line
The paper argues that when predicting bike demand across different years, you shouldn't try to predict everything at once. Instead:
- Separate the stable stuff from the changing stuff.
- Translate the changing stuff to look like the new year.
- Ignore the weird, noisy matches that don't make sense.
By doing this, the model becomes much more reliable, especially when the real-world data is messy or contains unexpected surprises.
Drowning in papers in your field?
Get daily digests of the most novel papers matching your research keywords — with technical summaries, in your language.