- Rating
- 2
- Confidence
- 3
- Informativeness
- 2
- Presentation
- 3
- Soundness
- 2
Read review
Paper summary
This paper studies cross-variate interaction for test-time adaptation in multivariate time-series forecasting under delayed supervision. CoRe models interactions among corrections produced by an existing output adapter, rather than directly mixing predictions from the frozen backbone. It combines a cross-variate mean anchor with shared-bottleneck refinement, modulated by a spectral gate computed from the input history. The evaluation compares correction-space and prediction-space interaction across forecasting backbones, datasets, forecast horizons, and additional adaptation methods.
Critical strengths
-
A clear design choice with strong comparative evidence. CoRe addresses a limitation of per-variate adaptation and compares its correction-space approach with COSA, its closest predecessor. Across the 168 configurations in Table 1, the reported mean per-setting relative MSE improvement is 10.57%, with 162/168 favorable comparisons. Both figures agree with the tabulated values and support the comparison.
-
Broad evaluation and a useful parameter-efficiency trade-off. The experiments cover multiple backbone families, additional adapters, multiple random seeds, interaction-space controls, and ablations of the anchor and gate. The detailed comparison with dense refinement shows similar aggregate accuracy, while the shared bottleneck requires substantially fewer additional refinement parameters. The resulting parameter-efficiency advantage supports the practical value of the architecture.
Critical weaknesses
-
Mechanism attribution and supporting result summaries need clarification. In Table 4, refinement without the shared anchor already improves performance by 7.1%, compared with 9.7% for the full method. The COSA+MLP control in Table 2 yields 0.97%, but the differences between this control and the no-anchor variant remain unclear. In addition, the aggregate improvements in Table 14 are not readily recoverable from the 168 detailed entries in Table 15. Averaging per-setting relative improvements over frozen backbones gives approximately 26.85% and 26.72% for the default and dense variants, respectively. These estimates differ from the reported improvements of 25.82% and 23.09%. These discrepancies complicate the interpretation and reproduction of the supporting comparisons.
-
The update timeline needs to be reconciled with the delayed-label protocol. The paper states that forecast targets become eligible for adaptation only after their labels have matured. In the supplied snapshot, the sequential path appears to update on the current batch's complete forecast targets before proceeding to adjacent windows. This could expose the adapter to information unavailable at the next forecast time. A small source-level test confirms this dependency in the supplied path, but does not reproduce the reported benchmark runs. The supplied COSA path also follows a similar update pattern. The authors therefore need to identify the code version and update timeline used for the reported results.
Questions for authors
-
Could the authors specify how the COSA+MLP, no-anchor, and prediction-space controls differ in input features, parameter sharing, gating, and optimization? Please also define the aggregation used in Tables 14–15 and identify the underlying runs. These details would clarify both the parameter-efficiency comparison and the contribution of the interaction space.
-
Could the authors provide a short time-indexed example or execution trace showing forecast issuance, label availability, and updates permitted before each subsequent forecast? Was the supplied adapt_simple() path used to produce Table 1? If so, please provide the main CoRe–COSA comparison with label maturation explicitly enforced.
Thank you for the source-level test and for recomputing our appendix tables; the trace you asked for is what exposed the leak. The code we adopted does not follow our stated protocol, and we did not verify it. Details and corrected results are in the General Response.
Q2. Yes, the supplied adapt_simple path (or a loop of the same structure) produced Table 1, and your trace is right.
Q1. Tables 2, 14 and 15 come from the leaky runs; your recomputation of Tables 14 and 15 is correct, and the mismatch is an error from compiling results.