- Rating
- 3
- Confidence
- 3
- Informativeness
- 2
- Presentation
- 3
- Soundness
- 2
Read review
Paper summary
Motivated by the observation that different time series may favor different detection criteria, this paper proposes TS-Router, a framework that uses TSFM to extract representation and uses a trained router to select top-k best anomaly detector and perform detection. The router is trained by minimizing the KL divergence between its predicted competence distribution and soft targets derived from detector performance on synthetic data. Experiments on 16 TSB-AD benchmarks show the best average rank across four metrics.
Critical strengths
-
The design is practical. “route-before-fit”(rbf) avoids running the whole pool on every target, needs no target labels, and the router is a simple MLP on a frozen encoder.
-
Solid and comprehensive experimental evaluation. Tab 1 shows results across 16 benchmarks and 4 metrics, with comparisons against both FM based and unsupervised anomaly detection methods. The ablations in tab 2 are also fairly thorough, comparing adaptive routing with fix selection, different fusion, as well as different TSFM and handcrafted features. The appendix provides further analyses of detector complementarity, top-k selection, detector pool size, and routing supervision. The comparisons with classical selectors under three different transfer settings are also a nice addition.
Critical weaknesses
-
There is limited modeling of cross-variable dependencies. The method handles multivariate time series through variable-wise routing and score aggregation, but it does not explicitly model interactions between variables, which may limit its ability to detect anomalies that arise from abnormal relationships across variables.
-
The results on multivariate benchmarks in Tab 7 also somewhat lacks consistency.
Questions for authors
-
There is a potential confounder in the encoder comparison. TimeRCD is pretrained using RCD synthetic data generation framework, which is also used to construct the router competence supervision. Its stronger routing performance in tab 2 may therefore partly come from this alignment, rather than better transferable temporal representations in general.
-
Could you provide an end-to-end runtime comparison between TS-Router and full ensembling? Since TS-Router only fits three detectors instead of eleven, it would be better to see how much runtime is actually saved by the rbf strategy.
4 comments
Response to Reviewer YofC (Part 2 of 2)
We now address the two concerns raised under Critical Weaknesses.
Response to Critical Weakness 1. We agree that channel-wise routing can miss anomalies that arise solely from changes in the relationships between variables, as noted in Section 6. For example, two sensors may fall out of sync while each still exhibits its usual temporal pattern. Our focus is on selecting specialists for the temporal behavior of each channel. A natural extension would be to use a joint representation of several channels to select specialists that model their interactions. For a fuller discussion, please see our response to Reviewer Jf2E’s Critical Weakness 4. There we discuss when channel-wise detection can be effective, examine the evidence across all five multivariate benchmarks, and explain how the routing framework could be extended to detect changes in cross-channel relationships.
Response to Critical Weakness 2. We appreciate your observation that TS-Router’s advantage varies across the multivariate benchmarks in Table 7. On VUS-PR, it ranks first on SMAP, second on PSM and SMD, and fourth on MSL and SWaT. It thus places among the top four on each dataset and achieves the highest mean VUS-PR (34.70) among the 15 methods when the five datasets are weighted equally. Its mean scores on the other metrics are also competitive: third on Standard-F1 and fourth on both Affiliation-F1 and event-level F1. For example, TS-Router ranks second on VUS-PR but eighth on event-level F1 on PSM, whereas on SWaT it ranks fourth on VUS-PR and first on Affiliation-F1. An independent analysis by Pinet et al., which included all five benchmark collections, found that changes in cross-channel correlation were often accompanied by a detectable deviation in at least one channel. This offers one reason why channel-wise routing can be useful on multivariate targets, even though its gains vary by dataset and metric. Your observation also points to a question we would like to study more directly: when does a multivariate system benefit from selecting specialists that model channels jointly? We plan to extend TS-Router to make that choice and evaluate it on faults that are detectable only through changes in cross-channel relationships.
Thank you again for your thoughtful review and constructive suggestions. We hope the additional experiments, analyses, and revisions address your concerns, and we would welcome any further questions or feedback.
As the discussion period is approaching its deadline, we would sincerely appreciate the opportunity to hear your thoughts on our response. We hope that the additional experiments and clarifications have addressed your concerns. Please feel free to raise any further questions or concerns, and we would be happy to address them while there is still time during the discussion period. We also welcome you to review our discussions with the other reviewers, where we provide additional explanations and results. Thank you again for your time and consideration.
Reply
Thanks for addressing my questions, and the clarifications did help. I would retain my positive rating.
Response to Reviewer YofC (Part 1 of 2)
Thank you for your thoughtful review. We appreciate your recognition of the practical value of our route-before-fit design and your positive assessment of the experiments and ablations. Your suggestions helped us clarify what the encoder comparison supports and quantify the time saved by routing before fitting. We have highlighted the changes in the revised PDF. We first respond to your two questions.
Response to Q1. Thank you for raising this point. We agree that the shared simulation framework is relevant when interpreting TimeRCD’s performance. In the default run reported in Table 2 (seed 42), all three pretrained encoders achieve higher NDCG@3 and downstream VUS-PR than any of the conventional representations. Across the 11 univariate benchmarks, Chronos, MOMENT, and TimeRCD achieve NDCG@3 scores of 0.698, 0.721, and 0.782, respectively, compared with 0.674 for the strongest conventional representation on this metric (Catch22). Their VUS-PR scores are 53.27, 53.89, and 56.36, compared with 51.31 for the strongest conventional result (MiniRocket). As you suggest, pretraining on data from the same simulation framework may partly explain TimeRCD’s lead over the other encoders; Table 2 does not isolate that effect. Chronos and MOMENT, however, were not pretrained with the RCD simulator. Their encoders remained frozen, and only their routing heads were trained on Syn-RCD competence targets, under the same protocol as the TimeRCD router. Notably, MOMENT even slightly exceeds TimeRCD on downstream Affiliation-F1 (88.50 vs. 88.11) and event-level F1 (49.74 vs. 49.62) in Table 2 despite having no exposure to RCD during pretraining. Their results support our broader conclusion: pretrained temporal representations can guide specialist selection even when the encoder was not pretrained with the simulator used to supervise the router.
Response to Q2. Thank you for suggesting an end-to-end comparison. We added a timing breakdown in Appendix B.2.8 (Table 14). Across the 11 univariate benchmarks, selecting three specialists before fitting them reduces mean runtime from 16.19 to 3.55 seconds per series, a 4.56× speedup over running all eleven specialists. Both measurements use the same hardware and include specialist fitting, scoring, normalization, and fusion. Of the 3.55 seconds for TS-Router, 3.52 seconds are spent fitting and scoring the selected specialists; all other steps, including encoding and routing, take about 0.03 seconds. On series with at least 100,000 observations, mean runtime falls from 138.16 to 29.10 seconds. TS-Router thus uses about 22% of the full ensemble’s runtime while improving mean VUS-PR from 49.54 to 56.36 on the same benchmarks (Tables 2 and 14). For comparisons with other detectors, including runtime, trainable parameter counts, and memory use, please see Table 15 and our response to Reviewer Jf2E’s Critical Weakness 5.