Back to Feed
Benchmarks & Evals

Fixing Forecast Collapse in Time-Series Models

Original: Forecast Collapse in Time-Series Foundation Models

Listen to the summary

Uses a voice available on your device

Audio options
On this page 4 sections
Related concepts 1 concepts

Key Takeaways

  • Identified forecast collapse as a failure where models produce flat predictions that cannot effectively rank financial assets.
  • Isolated two primary causes: limited predictability affecting point forecast amplitude and the failure of per-series objectives to capture cross-series structures.
  • Introduced CalibRank to balance squared error optimization with cross-sectional correlation.
  • Achieved nearly triple the cross-sectional correlation on the Finance1K dataset compared to traditional methods.

Summary & Methodology Analysis

Time-series foundation models often encounter forecast collapse, a failure mode where the model outputs nearly flat predictions during hourly return forecasting. This limits the model's utility for downstream tasks like ranking stocks, as the point forecasts lose their discriminative power. The authors identified that this issue stems from a combination of low predictability, which constrains the amplitude of calibrated point forecasts, and the reliance on per-series objectives that fail to account for relationships between different assets in the dataset.

To address these limitations, the paper introduces CalibRank, an objective function designed to improve forecasting performance by explicitly balancing two competing goals: minimizing squared errors and maximizing cross-sectional correlation. By optimizing for these concurrently, the method ensures that the model preserves the relative ranking of financial assets while maintaining accurate forecast amplitudes. This replaces or supplements the standard per-series optimization approaches that typically struggle to identify the underlying structural relationships in cross-series data.

Evaluation on the Finance1K dataset demonstrated that CalibRank consistently improves cross-sectional correlation across all tested models. The paper notes that conventional evaluation metrics are insufficient for detecting these issues because they focus on individual series metrics, which often obscure broader structural failures across the entire dataset. While the paper provides performance gains, it does not specify the latency impact or the computational resource requirements for training or inference with the CalibRank objective.

Interactive System Flowchart

Click diagram to expand and zoom

Cross-Examination & FAQs

A deeper dive clarifying mechanics, constraints, and baseline evaluations.

Q1. What is forecast collapse?

It is a phenomenon where time-series foundation models produce nearly flat predictions that fail to effectively rank assets.

Q2. What is the primary contribution of this paper?

The authors introduce CalibRank, a new objective function that fixes forecast collapse by balancing calibration and ranking objectives.

Q3. Does this work apply to all forecasting models?

The paper reports that CalibRank improved cross-sectional correlation across all tested forecasting models.

Q4. What are the two causes of forecast collapse?

The causes are low predictability limiting calibrated point forecast amplitude and per-series objectives failing to identify cross-series structures.

Q5. What dataset was used for evaluation?

The models were evaluated using the Finance1K dataset.

Q6. How does CalibRank perform compared to standard metrics?

On the Finance1K dataset, CalibRank nearly triples the cross-sectional correlation while keeping forecast amplitude near target levels.

Q7. Why are conventional evaluation metrics considered insufficient?

Per-series metrics can obscure structural failures that only appear when examining cross-series data.

Q8. Does CalibRank sacrifice forecast accuracy for better ranking?

No, CalibRank maintains forecast amplitude near target levels while simultaneously improving cross-sectional correlation.

Q9. What are the computational costs associated with CalibRank?

The paper does not specify the computational costs or latency implications of using CalibRank.

Flag an issue

What is wrong with this summary?

What is wrong?