- Rating
- 2
- Confidence
- 3
- Informativeness
- 2
- Presentation
- 2
- Soundness
- 2
Read review
Paper summary
This paper proposes TSRouter, a training-free framework for selecting time series foundation models from an evolving model zoo. TSRouter consists of three stages. PROFILE constructs model-specific capability regions using representative probe anchors and measured forecasting losses. ROUTE retrieves local capability evidence through a fixed Fourier-based representation and aggregates window/channel rankings to select a model. INSERT incorporates newly released models by evaluating them on existing anchors without retraining a selector. Experiments on 97 forecasting configurations from 23 datasets and 20 TSFMs show that TSRouter achieves a MASE of 1.508, outperforming the strongest evaluated baseline.
Critical strengths
- The separation into PROFILE, ROUTE, and INSERT is appealing. Reusing a fixed capability representation avoids retraining a supervised selector when the candidate pool changes.
- TSRouter-main improves MASE from 1.558 to 1.508 over the strongest evaluated deployable baseline, while achieving substantially lower routing overhead than online candidate probing.
Critical weaknesses
- TSRouter relies on 3000 anchors to characterize model capabilities and guide routing decisions. However, it remains unclear whether performance on these anchors reliably reflects model capabilities across diverse and unseen tasks.
- The proposed capability region construction relies on hard assignments of anchors to the best models. It is unclear whether this design offers advantages over other simpler designs, such as KNN-based aggregation of model losses on nearby anchors.
Questions for authors
- Why can anchors selected based on coverage in the time-series feature space reliably characterize the relative capabilities of different TSFMs? Have the authors compared alternative anchor selection strategies? Additionally, why does increasing the number of anchors from 3,000 to 5,000 lead to worse routing performance, as shown in Table 3?
- Could the authors compare TSRouter with simpler alternatives, such as kNN-based loss aggregation, to justify the proposed capability-region design?
Anchor Transfer, Budget Effects, and Direct-Loss Routing
Thank you for the constructive questions about anchor coverage and capability-region design.
Q1a — Why can anchors describe TSFM capability on unseen tasks?
Anchors and unseen task windows occupy the same representation space. Anchors attach measured model preferences to locations in this space, turning abstract task/model differences into measurable distances to model-specific support.
Appendix E, Table 9supports this transfer mechanism: identity features → Fourier with random anchors → Fourier with clustered anchors raises held-out anchor winner recovery from 0.076 → 0.396 → 0.446, and task recovery from 0.206 → 0.247 → 0.268. Thus, the representation and representative coverage jointly improve local preference transfer.Q1b — Were other anchor-selection strategies compared?
Yes—
Table 4explicitly ablates clustered versus random anchor selection. At the same 3,000-anchor budget and source allocation, random → clustered improves MASE 1.5172 → 1.5076 and CRPS 0.2385 → 0.2335, supporting representative sampling beyond anchor count alone.Table 4also separates source-removal and budget controls, showing how coverage and cost affect the operating point.Q1c — Why do 5,000 anchors perform worse?
Increasing the anchor budget rebuilds the supporting neighborhoods and can change model rankings; here, a few costly model switches outweigh gains elsewhere. The task-level diagnosis in
Appendix H.4 (new analysis)shows that, after increasing from 3,000 to 5,000 anchors, 59 of 97 tasks retain the same choice; among the 38 changed choices, 15 improve and 23 worsen. One COVID task accounts for 77% of the net MASE increase, so the higher average does not reflect uniformly worse routing. The MASE-difference 95% interval [−0.00252, 0.05372] includes zero. This illustrates a trade-off between anchor coverage, routing accuracy, and construction cost: a larger support set does not necessarily yield more accurate model selection.Q2 — Does region retrieval improve over kNN-loss?
Thank you for suggesting direct loss aggregation. We add a TSRouter-kNN variant that replaces region retrieval with nearby-loss aggregation, using the same 3,000 anchors, historical CRPS matrix, features, queries, and fusion (
Appendix H.2, Tables 11–13 (new experiment/analysis)). TSRouter-main improves MASE, while kNN has better CRPS point estimates. At the fixed k=10 with inverse-distance weighting:The MASE advantage survives multiplicity correction.
This is a difference in how anchors are used within the retrieval step: TSRouter-main retrieves model-specific winning support, while TSRouter-kNN aggregates losses over common neighbors. Both preserve the framework's core mechanism—reusing fixed anchor evidence for training-free routing and incorporating new models without retraining the selector. The comparison therefore clarifies a retrieval-rule trade-off within this framework.