- Rating
- 2
- Confidence
- 3
- Informativeness
- 2
- Presentation
- 2
- Soundness
- 2
Read review
Paper summary
The paper introduces Timer-M1, a multivariate time-series foundation model trained through temporal and relational primitive composition. A data pipeline combines real and generated source series into multivariate records, and forecasting episodes vary target/covariate roles and observation masks. The 121M-parameter model uses patch embeddings, temporal and cross-variate attention, learned layer-wise gates, and a quantile forecasting objective. Evaluation reports competitive results on FEV, TIME, and GIFT-Eval, selected primitive/reliability tests, and gate/data-construction ablations.
Critical strengths
-
The model supports univariate, joint-target, past-covariate, and known-future settings with a single compact backbone.
-
The work links data construction to observation availability instead of only increasing corpus size.
Critical weaknesses
-
The zero-shot generalization claim lacks a concrete training-data eligibility audit. The authors do not provide source identities, temporal cutoffs, deduplication, or target-interval overlap checks.
-
The primitive-learning explanation is under-specified and not sufficiently isolated. Appendix A gives representative operators rather than an executable generation recipe, and the supplied paper omits core optimization settings, consumed training exposure, source-mixture weights, and long-context post-training details. The data ablations do not document equal update/token budgets, and there is no same-data control isolating episode-role/supervision sampling or a held-out composition test. Thus the results do not yet establish whether its gain comes from primitive composition, different training exposure, or task design.
-
The improvement on these benchmarks seem marginal. for the primitive evaluation settings, Timer-M1 seems to be more advantageous since this is how its training data is constructed.
Questions for authors
1: Which exact GIFT-Eval and TIME training sources and time intervals enter pretraining and long-context post-training? Please provide the holdout/deduplication policy and target-interval overlap audit, plus results separated by training-source exposure where applicable.
2: What are the actual operator distributions, source-mixture weights, episode sampling distributions, optimization schedule, update/token budget, and compute for the main model and each ablation? Were the recipe comparisons matched for consumed training exposure rather than stored corpus size?
3: Does the primitive benefit survive matched-budget reruns and a held-out primitive-composition test? A same-data control that changes only episode-role/supervision sampling would also clarify whether the gains come from relational generation or the training task design.