- Rating
- 3
- Confidence
- 3
- Informativeness
- 2
- Presentation
- 3
- Soundness
- 2
Read review
Paper summary
This paper introduces Progressive Feedback Forecasting, a new forecasting paradigm that moves beyond conventional one-shot prediction by progressively incorporating newly revealed observations to revise the still-unseen future. Under this paradigm, the authors propose SHIFT, a framework that maintains multiple future hypotheses and dynamically updates them through causal belief filtering and recurrent trajectory assimilation. Extensive experiments on multiple real-world datasets demonstrate substantial performance improvements over conventional forecasting and online adaptation baselines.
Critical strengths
-
The paper introduces Progressive Feedback Forecasting, a novel forecasting paradigm that enables progressive forecast revision using newly revealed observations, offering a meaningful alternative to conventional one-shot forecasting.
-
SHIFT presents a well-designed framework that integrates multiple future hypotheses, causal belief filtering, and trajectory assimilation. Hindsight-teacher distillation further enables effective supervision while preserving causal inference.
-
The framework provides an interpretable feedback-driven forecasting process and supports efficient inference without online parameter updates.
Critical weaknesses
-
The paper does not explore how SHIFT handles noisy or missing feedback, which is quite common in real-world applications.
-
It is not very clear how SHIFT generates different future hypotheses from the same initial forecast and keeps them sufficiently diverse.
Questions for authors
-
Feedback may not always arrive on time. How would SHIFT perform when observations are revealed with some delay?
-
Could the authors explain how the feedback block size is chosen in practice? Would different applications need different settings?
-
Online forecasting and continual learning methods also use newly observed data to improve predictions. Could the authors explain more clearly how SHIFT differs from these approaches, especially in how feedback is used and what gets updated?