- Rating
- 2
- Confidence
- 2
- Informativeness
- 2
- Presentation
- 3
- Soundness
- 2
Read review
Paper summary
RestoreTS corrects potentially erroneous segments of historical data before forecasting and records the specific changes made. It is evaluated on eight datasets and five forecasting models. The experiments first introduce transient spikes and sustained value shifts, then compare forecasts before and after repair. Overall, forecasts become more accurate when using the repaired data.
Critical strengths
- Comparing forecasts from the same model before and after repair provides a relatively direct assessment of the repair’s impact. Improvements across multiple models also support the method’s applicability.
- The paper provides modification logs, input-quality analyses, and repeated experiments, and reports cases where performance deteriorates. These help clarify the method’s benefits and limitations.
Critical weaknesses
- Parameter selection relies on clean reference data and known corruption severity, and different settings may be used for clean and corrupted inputs. In addition, test data were examined during development. Performance under unknown corruption conditions and on new data therefore remains to be validated.
- On some datasets, more than half of the modifications move observations further away from the reference values. Under spike-only corruption, the average forecasting error also increases slightly. There is insufficient evidence that the method can effectively repair anomalies while preserving genuine changes.
Questions for authors
- How should parameters be selected when corruption severity is unknown? Can the same settings handle both clean and corrupted data?
- Did examining the test data influence the method’s design? Are results available for new time periods that were not used during development?
- In which intervals are observations made less accurate by repair primarily located, and by how much do their errors increase?
- What are RestoreTS’s main advantages over existing time-series repair methods?
4 comments
Follow-up on Rebuttal
Dear Reviewer ZfSU,
Thank you again for your thoughtful review. We have uploaded a revised manuscript incorporating the additional experiments and clarifications described in our response. In particular, we clarified the usage of corruption severity, investigated the wrongly edited intervals further and conducted our method on new time periods that were not used during development.
We would appreciate your feedback on whether these updates address your main concerns. If any points remain unclear, we would be happy to provide further clarification.
Thank you for your time and consideration.
Thank you for the careful response and for running these additional experiments. The clarification about severity labels is helpful, and the results on the new time period help address my concern about generalization beyond the data used during development.
I still have two main concerns. First, parameter selection continues to rely on clean validation references. The fixed-configuration results are encouraging, but they only cover Weather with PatchTST. It is still unclear how consistently this approach would work across other datasets and models when corruption conditions are unknown.
Second, the new analysis shows where harmful edits occur, but not how much they increase the error relative to the clean reference. Since most worsened edits affect originally uncorrupted values, their magnitude matters for judging whether the method preserves valid observations. I would also appreciate a clearer explanation of the performance drop under spike-only corruption.
Overall, the additional results make the forecasting benefits more convincing, but these remaining concerns still matter to my assessment. I therefore keep my current rating.
Thank you again for taking the comments seriously and putting effort into the additional analysis.
Thank you for the follow-up. We truly appreciate your time and the care you have given to the paper. We address the two remaining concerns below.
Concern 1: Extended Fix Configuration Experiments
We acknowledge that parameter selection rely on clean validation references in our method. However, clean references are needed only during initial parameter selection in our method. Even there are new unseen time series data inputs, we solely use the initial parameter selection in the new time series data without clean references.
We conducted one new experiment: we selected one restoration method and parameter set using only the 2020 validation references and applied it unchanged to the 2026 test period. No 2026 validation clean references or severity labels were used for selection or restoration. These results in the table below demonstrate that historical reference-based selection can support later deployment without repeating that selection for the evaluated period.
| Backbone | Raw MSE | Raw MAE | RestoreTS MSE | RestoreTS MAE |
|---|---|---|---|---|
| PatchTST | 0.4227 | 0.3828 | 0.3677 | 0.3566 |
| PatchLGA | 0.3826 | 0.3748 | 0.3525 | 0.3527 |
| DLinear | 0.5231 | 0.4086 | 0.4188 | 0.3800 |
| TimesNet | 0.9802 | 0.4820 | 0.5205 | 0.4279 |
| TimeMixer | 0.4318 | 0.3916 | 0.3610 | 0.3611 |
| iTransformer | 0.4905 | 0.3970 | 0.3886 | 0.3682 |
Following your suggestions, we extended our one fixed configuration experiments to eight datasets and all six backbones.
For each dataset, we selected one complete configuration using reconstruction MSE against clean validation references, averaged equally across L0–L5. We then used this one fixed configuration without supplying severity labels to selection or restoration.
The table below reports MAE reduction (%) versus the raw backbone. Errors are averaged equally over combined-corruption levels L1–L5 and horizons {96, 192, 336, 720} before computing the reduction. Positive values indicate improvement.
| Dataset | PatchTST | PatchLGA | DLinear | TimesNet | TimeMixer | iTransformer |
|---|---|---|---|---|---|---|
| ETTh1 | 0.28 | 0.27 | 0.17 | 1.27 | 0.39 | 0.58 |
| ETTh2 | 0.90 | 0.51 | 0.31 | 3.18 | 1.60 | 3.31 |
| ETTm1 | 6.53 | 6.00 | 5.74 | 8.49 | 8.13 | 8.07 |
| ETTm2 | 2.35 | 2.42 | 2.00 | 3.55 | 2.81 | 3.63 |
| Weather | 8.58 | 9.34 | 9.15 | 14.42 | 11.93 | 9.32 |
| AQWan | 6.16 | 7.49 | 5.16 | 7.26 | 6.78 | 5.38 |
| CzeLan | 15.71 | 14.46 | 7.90 | 17.63 | 15.96 | 12.00 |
| ZafNoo | 2.57 | 2.67 | 2.21 | 5.92 | 2.33 | 2.74 |
The extended experiments show consistent improvements across most tested datasets and forecasting models and these results provide broader evidence of effectiveness when corruption severity is unknown.
Concern 2: Error Magnitude & Performance Drop under Spikes
Thank you for clarifying this point. Our previous response focused on downstream forecasting errors, but your question concerned errors in the edited inputs relative to the clean reference. We apologize for this misunderstanding. Figure 1 (https://anonymous.4open.science/r/restorets-review-B9BB/rebuttal/figures/restorets_spike_failure.png) shows an ETTh1 spike-only example where 15 originally uncorrupted values at steps 141–155 are wrongly shifted. On these values, mean absolute input error increases from 0 to 3.448, and mean squared input error from 0 to 11.890. And the table below show the average magnitude of worsened edits on uncorrupted data across different datasets.
“Harmed (%)” is the percentage of originally uncorrupted values that RestoreTS changed. The error columns average only over those changed values. Their error relative to the clean reference was zero before restoration.
| Dataset | Harmed (%) | Mean added absolute error |
|---|---|---|
| ETTh1 | 0.13 | 2.660 |
| ETTh2 | 1.46 | 1.417 |
| ETTm1 | 0.23 | 2.350 |
| ETTm2 | 0.67 | 1.135 |
| Weather | 0.89 | 0.932 |
| AQWan | 1.50 | 1.657 |
| CzeLan | 0.34 | 1.032 |
| ZafNoo | 0.76 | 1.702 |
Regard a further explanation about the performance drop under spikes, RestoreTS focuses on temporary level shifts and is less effective for isolated spikes. In Figure 1 (https://anonymous.4open.science/r/restorets-review-B9BB/rebuttal/figures/restorets_spike_failure.png), the injected spikes remain unchanged, while an initially uncorrupted interval is translated to an incorrect level. This indicated the reason why the performance degraded than the baseline model, which added more worsened regions into the inputs than the one that baseline model received. This shows that adding spikes can alter the correction decisions and trigger harmful changes to a part of clean observations. We acknowledge this weakness and the need to improve selectivity under spike-only corruption.
Thank you for your insightful and careful feedback and reconsideration.
Thank you for the thoughtful review. Updated code is in the anonymous repository linked on line 26.
Q1/W1: Unknown Severity and the Same Settings
We apologize for the ambiguous wording. Severity is not a necessary input. Originally, validation reconstruction error selected each severity's configuration; the label retrieved it during testing. Restoration then used the observed history and selected parameters (Algorithm 1).
In the hidden-label replay, clean validation references selected configurations without severity labels. Across eight datasets with PatchTST and seed-2021 checkpoints, all choices matched Appendix A.1 and forecasts agreed to floating-point precision in the table below.
Values below average horizons and severity levels. "Both versions" means original and hidden-label versions are the same values. The results indicate that severity is not a necessary input.
we evaluated one fixed configuration on Weather/PatchTST. We chose one fixed configurations setting by mean validation reconstruction MSE across L0–L5 with equal condition weights. And we applied the same settings to every test under different severities.
“Specific” selects per severity; “fixed” uses one choice. Both RestoreTS columns use PatchTST. MSE/MAE average four horizons.
The fixed choice matches the original at L1–L5. On L0, MSE increases by 0.50% versus raw PatchTST while MAE decreases by 0.11%, which suggests the necessity of our validation selection module.
Q2/W1: Method Design and Generalization
BOCD observations on training and validation histories motivated our design: it partitions histories into runs and exposes changes between them.
Following your suggestion, we evaluated 2026 Beutenberg weather data from Jena: September 11–30 for validation and October 1–November 9 for testing. The test period occurred after the submission deadline.
We reused seed-2021 checkpoints and selected settings on new validation histories. Results average four horizons and L0–L5.
These results support our method can generalize to an untouched new time period that were not used during the method development.
Q3/W2: Worsened Edits
Some edits worsen accuracy. Both columns use all worsened edits as the denominator and sum to 100%.
Most worsened edits affect initially correct values (uncorrupted data). Appendix C, Table 12 gives improved/worsened fractions. These frequencies do not quantify error increases. Forecasting shows aggregate benefits despite harmful edits. Our study does not establish a general relationship between individual corrections and forecasting error.
Q4: Main Advantages
Table 23 compares filters before the same PatchTST backbone. Under shift-only corruption, RestoreTS reduces MSE/MAE by 7.45%/5.97%. Median and Hampel increase MSE by 2.88% and 2.43%.
We will clarify severity-label usage in Section 3.4 and Appendix A and add the new results to Section 4. Thank you for your insightful feedback and reconsideration.
[1] Aoqian Zhang et al. Multivariate Time Series Cleaning under Speed Constraints. PACMMOD, 2024.
[2] Chenyang Li et al. EDITOR: Multi-Resolution Cleaning of Multivariate Time Series via Detect-Localize-Repair. ICDE, 2026.