- Rating
- 4
- Confidence
- 3
- Informativeness
- 2
- Presentation
- 3
- Soundness
- 2
Read review
Paper summary
The paper proposes SPECTOR, a compiler for compositional time-series priors. Kernel subtrees are dispatched to spectral sampling, finite-rank features, Gaussian modulation, state-space simulation, or independent path composition, avoiding dense covariance factorization where the representation permits. The general construction preserves covariance; stronger Gaussian-law guarantees apply to suitable subclasses or asymptotically in the spectral feature count. The instantiated generator is evaluated through synthetic pretraining across six architectures and three forecasting benchmark suites.
Critical strengths
-
The compiler offers an extensible way to generate diverse priors efficiently. The theory distinguishes covariance preservation from Gaussian-law preservation and states the conditions for linear scaling.
-
SPECTOR leads all 18 architecture–benchmark aggregates. The gains remain with shared augmentation and when only the sampler changes under a fixed 10M-example budget (Tables 24–26). These controls make the downstream benefit convincing.
Critical weaknesses
- SPECTOR’s instantiated prior is manually specified through 18 primitives, sampling weights, composition rules, and augmentation settings such as SCM mixing, quantization, and spike injection. The bank and augmentation ablations are useful, but sensitivity to the specific weights and augmentation probabilities remains unclear. Testing alternative configurations would help establish how robust the results are to these design choices.
- All forecasting evaluations use univariate inference: multivariate targets are split into separate series, and exogenous covariates are ignored (p.6, L292–294). Although the SCM augmentation generates correlated series, its value for forecasting with cross-variable dependencies remains untested. A native multivariate or covariate-aware evaluation would strengthen the evidence for this component.
Questions for authors
- How sensitive are the forecasting gains to the primitive sampling weights and augmentation probabilities? Do reasonable alternative configurations retain comparable performance?
- Does the SCM augmentation benefit native multivariate or covariate-aware forecasting? A comparison with and without SCM in a setting that explicitly uses cross-variable information would help establish its value beyond univariate prediction.
2 comments
Response 2/2
W2 + Q2. Does the SCM augmentation benefit native multivariate or covariate-aware forecasting? A comparison with and without SCM in a setting that explicitly uses cross-variable information would help establish its value beyond univariate prediction.
Thank you for the insightful question. Among the six architectures we study, Chronos-2 is the only one that supports both multivariate targets and covariates. To test whether the SCM structure in SPECTOR helps when the model actually uses cross-variable information, we pretrained two variants of Chronos-2 on the same SCM-generated SPECTOR series. They differ only in whether the SCM group structure is exposed to the model (we believe this is a cleaner setup, since removal of SCM from the generation pipeline would also change marginal distributions):
- SPECTOR, 100% univariate: All SPECTOR series are passed as univariate series (no shared group IDs) during Chronos-2 training
- SPECTOR, 50% univariate, 25% multivariate, 25% covariate: A training batch is composed of 50% univariate series, 25% multivariate groups and 25% covariate groups passed to Chronos-2 during training. For the multivariate and covaraite group, the series belonging to the same SCM share the same group IDs, randomly split into multivariate targets or covariates.
All models are evaluated on FEV-Bench with multivariate and covariate-aware inference, so the model receives all target channels and the provided covariates. The table below (added as Table 29, Appendix J.10) shows that mixed covariate/multivariate aware pretraining improves aggregate skill in all three task groups. The largest gain was on covariate-aware tasks (+5.33 points), with a smaller gain on multivariate tasks (+0.56 points). These preliminary results demonstrate a direct path from SPECTOR’s existing generator to multivariate pretraining. Designing richer dependencies between targets and covariates is a separate research question that warrants a dedicated study. We have updated the Limitations section accordingly.
| Training | Inference | Univariate (32) | Multivariate (26) | Covariate (42) |
|---|---|---|---|---|
| SPECTOR, 100% univariate | multivariate + covariate | 33.66 | 55.46 | 38.40 |
| SPECTOR, 50% univariate + 25% multivariate + 25% covariate (via SCM) | multivariate + covariate | 35.53 (+1.87) | 56.02 (+0.56) | 43.73 (+5.33) |
FEV-Bench SQL skill score (%, higher is better). Values in parentheses are gains/losses in percentage points over SPECTOR 100% univariate.
Summary
Thank you again for your detailed and positive review; we believe it has substantially improved our paper. The revised manuscript adds a sensitivity analysis to the base-kernel weights and augmentation probabilities (Appendix J.11) and native multivariate and covariate-aware pretraining and inference (Appendix J.10). We hope these additions address your concerns, and we would be glad to answer any further questions.
Response 1/2
We are grateful for your positive assessment of our work, and for recognizing the extensibility and efficiency of our framework together with its strong pretraining performance. Following your suggestions, we added a sensitivity analysis of SPECTOR to its base-kernel sampling weights and augmentation probabilities (Appendix J.11), and experiments with native multivariate and covariate-aware pretraining and inference (Appendix J.10). Our detailed point by point response appears below.
Following your suggestion, we ran experiments that vary the primitive sampling weights and augmentation probabilities to test how robust SPECTOR is to these hyperparameters. The bank has 18 base kernels, and to analyze the sensitivity in a more efficient way, we rescale all weights jointly with a temperature-style exponent, pk(α)∝wkα: α<1 flattens the distribution toward uniform and α>1 concentrates it on the highest-weighted primitives. We trained PatchTST on four variants, using the training procedure in Appendix H.1. B1 and B2 flatten or sharpen the sampling weights, with α=0.5 and α=1.5 respectively. B3 lowers the SCM probability from 1.0 to 0.5, and B4 lowers the value-transform probability from 0.5 to 0.25. The table below (also added to Appendix J.11) reports aggregate skill on each benchmark (PatchTST, skill %, higher is better), with CauKer, the strongest baseline generator, for reference. All four variants remain above CauKer. Compared with SPECTOR default, the largest change in aggregate skill is 1.71 percentage points on M-Series, 1.21 on GIFT-Eval and 0.55 on FEV-Bench. No variant dominates: each improves on at least one benchmark and lowers skill on another. The default is therefore not a sharp optimum, and SPECTOR's advantage over other synthetic priors does not depend on the exact weights or augmentation probabilities.