- Rating
- 3(+1)
- Confidence
- 2
- Informativeness
- 2
- Presentation
- 3
- Soundness
- 2
Read review
Paper summary
This work proposes Parallax, a method for correcting time series predictions. It starts from the observation that averaged fine predictions can differ from coarse predictions. The method uses this difference to correct the fine predictions. It fits a linear correction using past predictions and their true values. It mixes error statistics based on time scales with those calculated directly from the same past records. The time scales and mixing weight are selected using validation data. The results show improvements across different models, including foundation models and models that already use multiple time scales.
Critical strengths
- The method improves different types of forecasting models, including strong baselines, foundation models, and models that already use multiple time scales. I believe showing that a simple correction can help these different models is a practical contribution of this work.
- Ablations show that it helps to consider how reliable the coarse predictions are. Using more details from past errors also brings further gains. These results support the design and help explain why each part is included.
Critical weaknesses
- Parallax improves predictions through a separate correction step, which requires additional fitting and inference time. Its improvement therefore comes with a time cost. If a foundation model could learn during pretraining to make averaged fine predictions agree with coarse predictions, this extra correction step might be less necessary.
- Parallax keeps the correction fixed after fitting. In a streaming environment, error patterns may change, making the fixed correction less useful. Updating it requires additional fitting time, creating a trade-off between keeping the correction useful and its update cost. Although Appendix E acknowledges this risk, the paper does not evaluate how often updates are needed or whether their gains justify the extra cost.
Questions for authors
The weaknesses above are my main concerns. Addressing them would have the greatest impact on my assessment. I also have the following questions:
- How much past data do the fine and coarse models use? If the coarse model sees a longer period of data, can you separate the benefit of this extra information from the benefit of Parallax? Does Parallax still help when the fine model sees the same period of past data?
- Do the reported running times include preparing the inputs, making all fine and coarse predictions, and applying the correction? How long does it take to update the correction module? This would help assess whether the method can be used in streaming settings and how often it can be updated.
- How much past data is needed to fit a reliable correction? Do the results change much when less or more past data is used?
- Foundation models can be used across datasets, but Parallax still fits a correction for each dataset. Appendix D.5 shows that several mixing weights work well with LightGTS. Does this also hold for the other foundation models? Such a comparison would help clarify how much dataset-specific tuning is needed and could be useful for developing more general post-hoc methods.
5 comments
Response to the Reviewer b1iz (W1 Part 2, W2)
W1 (Part 2): If a foundation model could learn during pretraining to make averaged fine predictions agree with coarse predictions, this extra correction step might be less necessary.
We agree that such pretraining could reduce the disagreement, but agreement does not guarantee a smaller error. By Eq. (1), the disagreement $ \mathbf{d}_k = (\hat{\mathbf{y}}^{(k)} - \mathbf{A}_k\mathbf{y}) - (\mathbf{A}_k\hat{\mathbf{y}}^{(1)} - \mathbf{A}_k\mathbf{y})$, so can mean that the two views make the same error on every block mean, not that this error is small (Section 3.1). For example, if the coarse forecast and the averaged fine forecast both predict 10 for a block whose true mean is 12, they agree but both are off by 2. Our results also show that although reconciliation methods enforce this agreement on the same forecasts, they increase MSE on up to 13 of the 20 dataset-backbone pairs, while Parallax improves all 20 (see Table 15, Appendix D.3.2, Page 36-38). Parallax also improves backbones that process several resolutions internally by up to 26.4% and recent foundation models by up to 37.6% in average MSE (see Section 4.1, Tables 1 and 11, Page 6 and 30). Thus, the correction remains useful for models that already learn across scales.
W2: Parallax keeps the correction fixed after fitting. In a streaming environment, error patterns may change, making the fixed correction less useful. Updating it requires additional fitting time, creating a trade-off between keeping the correction useful and its update cost. Although Appendix E acknowledges this risk, the paper does not evaluate how often updates are needed or whether their gains justify the extra cost.
We evaluated both how often updates are needed and whether they justify their cost on LightGTS (H=96, 7 datasets). Every H, 4H or 16H test windows, we refit the Parallax corrector on the most recent data, using the same number of windows as the training set, reusing their forecasts with the chain and λ fixed. We compare it with δ-Adapter (ICLR 2026), which is updated by one gradient step per window. As shown in Table R3 below, Parallax fitted once already beats this online δ-Adapter, and refitting every 16H windows costs at most 86.8 ms per test window.
Table R3: Updating Parallax and δ-Adapter on LightGTS (H=96). "Fitted once" uses the Parallax corrector fitted on the training set for the whole test set. With "refit every kH" (k=1, 4, or 16), we fit a new corrector after every kH test windows on the most recent data using the same number of windows as the training set and use it for the next kH test windows. Negative ΔMSE means improvement over LightGTS alone. Update time is the CPU time of one Parallax refit divided by the number of test windows between two refits.The sampling interval of each dataset is given in parentheses.
| Dataset | ΔMSE, δ-Adapter online | ΔMSE, Parallax fitted once | ΔMSE, Parallax refit every H | ΔMSE, Parallax refit every 4H | ΔMSE, Parallax refit every 16H | Parallax update time per test window (ms): refit every H / 4H / 16H |
|---|---|---|---|---|---|---|
| ETTh1 (1 h) | −0.47% | −13.41% | −13.79% | −13.76% | −13.32% | 8.5 / 2.1 / 0.5 |
| ETTh2 (1 h) | −0.29% | −4.92% | −4.28% | −4.04% | −4.52% | 8.7 / 2.2 / 0.5 |
| ETTm1 (15 min) | −0.97% | −64.02% | −64.19% | −64.21% | −64.13% | 46.7 / 11.7 / 2.9 |
| ETTm2 (15 min) | −0.89% | −26.19% | −25.82% | −25.86% | −25.91% | 47.8 / 11.9 / 3.0 |
| Weather (10 min) | −8.84% | −32.75% | −34.01% | −33.99% | −33.99% | 135.3 / 33.8 / 8.5 |
| Electricity (1 h) | −13.99% | −49.88% | −50.13% | −50.05% | −49.92% | 1,389.5 / 347.4 / 86.8 |
| Solar-Energy (10 min) | −11.52% | −84.15% | −84.70% | −84.73% | −84.69% | 640.5 / 160.1 / 40.0 |
On the studied benchmarks, a Parallax correction fitted once stays useful over time. In the standard setting, the corrector is already kept fixed over the whole test set, as in the "fitted once" column of Table R3. To check for a decline within this period, we take 3 settings of Table R3 (Parallax fitted once, Parallax refit every H and the online δ-Adapter), split their test windows into 4 consecutive quarters in time order, and on each quarter compare the MSE of each setting with that of LightGTS alone on the same windows (see Figure 10, Appendix D.6, Page 44). Parallax fitted once beats the online δ-Adapter in every quarter and still reduces MSE by 4.2% to 78.5% in the last one. Refitting every H windows changes this by at most 2.1 points, so what Parallax learns stays valid over time.
Response to the Reviewer b1iz (Q1, Q2)
Q1: How much past data do the fine and coarse models use? If the coarse model sees a longer period of data, can you separate the benefit of this extra information from the benefit of Parallax? Does Parallax still help when the fine model sees the same period of past data?
In short, yes, the benefit of the longer history can be separated from that of Parallax, and Parallax still helps even when the coarse forecasts see less history than the fine model.
- “How much past data do the fine and coarse models use?”
The fine model sees L = 96 time steps (36 on ILI), as in the standard benchmarks. With foundation models, the same frozen model forecasts each coarse resolution k from 96 block means, covering 96k original steps. With task-specific models, an independent coarse model is trained for each k, and its lookback is chosen on validation from 96 and max(4, ⌊96/k⌋) block means. We have clarified this protocol in Appendices C.1 and C.4.
- “If the coarse model sees a longer period of data, can you separate the benefit of this extra information from the benefit of Parallax? Does Parallax still help when the fine model sees the same period of past data?”
Yes to both. We rerun Parallax on LightGTS with the same frozen model at every resolution and limit the history of the coarse forecasts to the 96 steps of the fine model (same history) or to the last 48 of them (half history). Parallax still reduces MSE on all 7 datasets and keeps 84% of its gain with the same history and 82% with half of it (Table R4 below).
Table R4: Parallax on LightGTS with the history of the coarse forecasts controlled. ΔMSE shows improvement compared to LightGTS only, averaged over 4 horizons.
| Dataset | ΔMSE, standard setting (coarse sees 96k steps) | ΔMSE, same history (all resolutions ≤ 96 steps) | ΔMSE, half history (coarse sees 48 steps) |
|---|---|---|---|
| ETTh1 | −10.82% | −9.87% | −9.41% |
| ETTh2 | −6.94% | −2.51% | −1.91% |
| ETTm1 | −54.66% | −49.74% | −49.19% |
| ETTm2 | −19.39% | −11.59% | −10.60% |
| Weather | −25.79% | −14.55% | −14.32% |
| Solar-Energy | −79.83% | −73.19% | −72.62% |
| Electricity | −49.46% | −44.99% | −43.75% |
| Average | −35.27% | −29.49% | −28.83% |
| Improvement retained | 84% | 82% |
The gain remains because, even when the coarse forecasts see the same or a shorter history than the fine forecast, the frozen model makes different errors at the coarse resolution. So, the disagreement between the coarse forecast and the aggregated fine forecast carries information about the fine-resolution forecast errors, and Parallax uses this information to correct the fine forecast (Section 3.1).
Q2 (Part 1): Do the reported running times include preparing the inputs, making all fine and coarse predictions, and applying the correction?
Please refer to W1 (Part 1) above.
Q2 (Part 2): How long does it take to update the correction module? This would help assess whether the method can be used in streaming settings and how often it can be updated.
Updating the corrector costs 8.5 ms to 1,389.5 ms per test window with LightGTS on the 7 datasets when refitting every H windows (Table R3 above), since it only re-estimates closed-form moments from existing forecasts, with no forward pass or gradient training. This is shorter than the interval between two observations (10 minutes to 1 hour), so even refitting every H windows is affordable in streaming. Such frequent refits are rarely needed on these benchmarks. Refitting changes the MSE reduction little on every dataset, and refitting every 16H windows, at 0.5 ms to 86.8 ms per test window, stays close to refitting every H windows. Deciding when to refit under stronger shifts, particularly in streaming settings, is beyond the paper's focus and remains open. We revised Appendix E to clarify these limitations and scope of the paper.
Response to the Reviewer b1iz (W1 Part 1)
We sincerely thank you for the constructive comments, which have helped us to improve our paper. We provide new experiments for each point, and all results have been added to the revised paper (in blue-colored text).
We agree that the Parallax correction adds time, and we have now measured it for each stage, compared with δ-Adapter (ICLR 2026) and RGMR (ICML 2026) (see Table R1 below, full results in Table 18, Appendix D.6, Page 43). The additional time is small and in return Parallax achieves the largest MSE reductions among the 3 correctors. For each window, Parallax takes 1.01 to 3.07 times as long as the backbone alone, while reducing MSE by up to 64.8%.
Table R1. Cost and accuracy of the post-hoc correctors at H=96, with LightGTS, Toto-2.0-4m, and Toto-2.0-22m on ETTm1, Weather, and Electricity. Time per window covers: coarse-input preparation + all fine and coarse forecasts + the correction, relative to the backbone alone. Fitting time includes the forecasts for fitting and chain selection, and storage excludes the backbone. Negative ΔMSE means improvement over backbone.
For task-specific backbones, the coarse models add a one-time training cost, which we report in our answer to the Reviewer C45Z, Q3. We summarize the results, including training, inference, and storage costs of Parallax for 3 foundation models and for OLinear, in Table R2 below.
Table R2: Costs (additional training time, storage, time per window, and correction time) added by Parallax over ETTm1, Weather, and Electricity at H=96. Per-window time covers coarse-input preparation, all fine and coarse forecasts, and the correction time. Models are trained on GPU, and the corrector is fitted on CPU. Foundation models have no additional training stage for coarse levels. For OLinear, the additional training time is relative to training the backbone alone. Negative ΔMSE means improvement over backbone alone.
As seen in Tables R1 and R2 above (see full results in Table 18, Appendix D.6, Page 43), the correction itself is almost free (about 0.2 ms against 8.23 to 68.23 ms for the whole window in Table R2), so nearly all of the time is spent on producing the forecasts. Parallax builds the cross-resolution disagreement from these forecasts and uses it to reduce MSE by up to 64.8% on the 3 datasets.