- Rating
- 1
- Confidence
- 2
- Informativeness
- 1
- Presentation
- 1
- Soundness
- 1
Read review
Paper summary
From the abstract, the authors supposedly propose CovLift which "screens engineered covariates against observed history and matches features and context length to the forecasting model" - but I do not understand what that means, because the paper does not explain that well.
As for the results, I understand nothing.
Critical strengths
Only if I could undersatnd the paper can I even judge it. I see no critical strengths as the entire paper was completely incomprehensible.
Critical weaknesses
The paper is incomprehensible as written. I was unable to understand anything, let alone evaluate it
The examples below are taken from the first few pages; the same pattern continues through Section 3, after which I could no longer follow the paper. I list them so the authors and the ACs can see the problem concretely.
- Abstract: "On spring electricity load with day-1 weather forecasts, eight added features harm Chronos-2 at 128 observations but reduce its geometric paired mean squared error ratio by 24% against same-length raw covariates at 1,024."
- What does this mean? There is no context given before these results; it jumps into low-level results directly.
- Introduction: "A day-ahead temperature forecast cuts error tenfold for a temperature target (§4), yet can harm other targets. We study this undergeneralization across synthetic probes, energy, retail and benchmark tasks (§3–4; Fig. 1)."
- What does this mean?
- What is "Rounds-2/3"? Only explained in §6.
- What is "spring load"? Is this a dataset? It is never introduced or cited in the main text.
- What is a "preregistered contrast"?
- What is a "reader"? Never defined.
- What's a "channel" (Fig. 1)? Covariate? Feature?
- "328 spring load windows" (Fig. 1 caption) - what is that? Is this a dataset? Which windows?
- "Intervals and fixed-identity controls" (Fig. 1 caption) - what are you talking about? What does any of this mean?
- Figure 1 is incomprehensible.
- "vintages"? What is that? Never defined.
- "Orthogonal probabilist–Hermite probes" - what is this? This is used for the first time on page 4 and onwards but never defined; no citation/reference.
Questions for authors
See weaknesses. I have nothing more to ask/clarify as I did not understand anything.
Response to Reviewer 8Pot: clarity, results and AI use
We thank the reviewer for identifying unclear passages. After using these terms throughout months of research, we became too accustomed to them and did not introduce them clearly enough for readers. We take responsibility for this presentation issue. We apologise for the delay while verifying additional experiments. We will introduce the task, data and terms before the results.
What problem does the paper address? A pretrained forecasting model may fail to use helpful information, such as weather forecasts. We study when this happens and whether changing the inputs can improve predictions while keeping the model's weights fixed.
What does CovLift do? CovLift constructs features from existing covariates, such as squared temperature, and screens them using observed history. It does not use future target values. A synthetic capacity profile measures which relationships each model can use. Our load gains come from expansion and screening; an additional selection benefit from the profile remains unestablished.
What does the abstract result mean? On spring electricity demand, eight added features hurt Chronos-2 with shorter histories and help with longer histories. Keeping feature identities fixed also supports the role of history length. This shows why features and history should be assessed together. These results use the original weather feed, whose timing limitation is explained below.
The terms and Figure 1.
Scientific significance. The additional experiment shows that screened expansion can improve forecasts in unseen regions without updating model weights. Ridge also benefits from longer histories, while Chronos-2 shows greater sensitivity to irrelevant added features in our controls. Practically, this supports choosing features and history jointly for the model and task. The weather test remains conditional on an assumed publication delay because actual release times are unavailable.
Did we verify the AI-assisted work? Yes. We verified the code, results, citations and text, and take responsibility for the submission. We disclosed AI assistance in the submission form and AI Use Statement. The questions, hypotheses, designs and interpretations are ours. The supplement provides code and per-window evidence for submitted results, including failed tests.
We view this work as a small step towards addressing under-generalisation in time-series foundation models through covariate engineering. If this approach generalises, it could help frozen models use task-specific information, such as weather for energy demand or promotions for retail, without retraining for each task. We would appreciate it if the reviewer could assess the paper's scientific contribution using these explanations and the evidence in our responses to gZos and S1Fx, and reconsider the score and the flag. We thank the reviewer for helping us clarify the work.