- Rating
- 2
- Confidence
- 3
- Informativeness
- 2
- Presentation
- 2
- Soundness
- 3
Read review
Paper summary
The paper studies the inductive biases in time series modeling. It designs a methodology to analyze the impact of each design component on the performance of the model. Its studied design components range from normalization to local patching, and its analyzed use cases include forecasting, RUL, and anomaly detection. The findings are used to design time series models with the appropriate inductive bias for a given task.
Critical strengths
- The paper touches on an important question in time series tasks, since the inductive biases in time series modeling play a very significant role, which is not necessarily involved in other domains, making the analysis very relevant.
- The paper covers a relatively comprehensive list of aspects in the design of time series models, and the analysis has been shown on not only for forecasting tasks, but also for applications beyond.
Critical weaknesses
- I feel that the presentation of the paper needs to be improved, as well as its positioning. In particular, it should be made clearer whether the major contribution of the paper is a method to analyze the inductive biases in time series modeling, or the insights derived from it. In terms of the results in section 4, I find them too densely presented. The paper needs to better highlight the main takeaways.
- The paper mainly focuses on ablating every single design choice in the model, but there are two major questions that need to be answered more clearly:
- How does that differ from a standard ablation study that people have already been doing?
- Can the method handle cases where more than one inductive bias interacts with each other, showing a high correlation?
Questions for authors
- How specific is the proposed method for time series modeling? That is, can a similar method/framework be adopted in other domains, such as computer vision and natural language processing? An answer to this question can better position the significance of One-Core.
- Does the analysis apply only to a specific problem with a specific dataset? For example, can a similar analysis be done on a time series foundation model to reveal the inductive biases of the model, and potentially relate it to the properties of its downstream tasks?
2 comments
Follow-up on our response
Thank you again for your review. Our response and revised manuscript clarify the contribution, the distinction from standard ablations, interactions between design choices, and potential applicability to other domains and foundation models.
As the discussion period draws to a close, we would appreciate any feedback on whether any of your original concerns remain unresolved.
Reply to Reviewer iG5J
Thank you for asking us to clarify the relationship between the method and the findings. ONE-Core's primary contribution is a controlled procedure for determining which design decisions are supported by matched interventions and held-out evaluation within a stated scope. In v8, Figure 1 shows the workflow from descriptors and matched interventions to admission decisions. Section 3 describes the shared architecture before the experiments. Table 2 connects the evidence to each bias decision, and Section 4 opens each task's results with FIX, CONDITION, or ABSTAIN.
From matched ablations to design decisions
A matched ablation measures the response to a design change with other model choices held fixed. ONE-Core uses that evidence to determine which design decision is supported within a stated model family, candidate set, and evaluation protocol. A supported fixed choice (FIX), an admitted conditional override (CONDITION), and retaining the prior when evidence is insufficient (ABSTAIN) are three outcomes of the same procedure. For a specified descriptor and rule class, we fit the threshold and leaf actions outside each held-out dataset or subset. A conditional override must lower mean held-out regret relative to the best fixed choice and match or improve on that choice in at least two-thirds of folds.
In the original six-dataset H96 abstraction audit, the matched comparison identified 32→8 as the lower-regret fixed choice (0.49% versus 1.09% for Single-8). The context-memory rule tied it at 0.49%, so the testbed yields a fixed starting configuration for that protocol and candidate set (FIX). For RevIN, the selected descriptor rule yielded 2.11% mean regret versus 10.15% for fixed RevIN and met the fold criterion (CONDITION). The RevIN evidence is conditional on the selected descriptor and rule class within the original 12-dataset audit. Across two selected external targets, the frozen RevIN rule had higher mean regret than fixed RevIN. The anomaly detection evidence-source audit recorded heterogeneous responses and abstained from routing (ABSTAIN). Each decision records what the available evidence supports. Performance on a new dataset requires a separate evaluation.
V8 also adds a deterministic reuse diagnostic (Table 5; Appendix E). At budget four, evidence-based revalidation priority yields 0.431% mean regret versus 1.405% for random allocation. All budgets are reported, including a loss at budget one. This retrospective cross-fitted replay uses oracle correction and shared development rows; its three-budget adjusted tail fraction is 0.105. It illustrates a bounded downstream use of the response record, without establishing transfer or a newly admitted rule.
Interactions among design choices
For two binary choices, a matched 2×2 design measures each intervention at both settings of the other. In the Weather H96 experiment, removing RevIN lowered mean MSE from 0.1711 to 0.1634 with Patch and from 0.1741 to 0.1670 with LocalFull. The estimated interaction is about 0.0006 MSE in magnitude, using the rounded means (v8 §3, p. 7 and Table 19).
Before adopting multiple changes together, ONE-Core compares the measured joint configuration with the retained one. The RUL audit tested a joint change to locality, abstraction, and width and retained the capacity policy. On FD002, the mean paired gain against that policy was +0.11% (95% CI [−5.08%, +5.30%]). The interval includes zero and the gain falls below the 0.5% practical margin, so the audit records a tie (v8 Table 36). The one-axis audits measure each change separately. The joint comparison measures their combined effect. Estimating pairwise interactions would require intermediate configurations.
Applicability beyond the evaluated model family
The admission protocol could be instantiated in vision or language using matched interventions, domain-specific metrics and held-out units, and training-data descriptors for any proposed conditional rule. For a time-series foundation model, an initial application could hold the pretrained backbone fixed and compare two adapters or readouts under the same downstream task and tuning budget. A question about the bias of the pretrained architecture itself would require matched pretraining comparisons. The descriptor catalogue and empirical findings in this paper cover the evaluated forecasting, RUL, and anomaly detection settings within the ONE-Core model family.