Additional Rebuttal (Optional Reading) # Part 1
**Dear Reviewer 24Zo,**
Thanks again for you careful review. **It’s the discussion phase now, so we would like to continue to address the uncovered points from the rebuttal phase** (*due to the text length limits in the rebuttal*). *If you find these additional comments any inappropriate (e.g., out of rebuttal limits), please ignore these comments.*
> Finally, despite being describes as main baselines, why SparseTSF was not included in this paper? Especially, as SparseTSF seems to produce better results than proposal especially for ETT and not for Electricity and Traffic. What would be the reason for such differences?
As mentioned in the rebuttal, we noticed SparseTSF, which was recently accepted at ICML 2024, because it emphasizes the importance of periodicity in long-term forecasting tasks, similar to our work. Thus, we included it in the related work but did not perform a complete comparison due to the submission deadline constraints. We will supplement a complete comparison in the revised paper.
Additionally, SparseTSF performs better on the ETT dataset rather than the Electricity and Traffic datasets for two reasons. First, **the ETT dataset is smaller and noisier**. In such cases, the sparse techniques proposed in SparseTSF help the model focus more directly on corresponding elements in historical cycles, reducing interference from less relevant elements and improving overall performance. Second, the ETT dataset's dimensionality (number of channels) is significantly lower than that of the Electricity and Traffic datasets, with the former having only 7 channels compared to the latter's 321 and 862 channels. Note that SparseTSF fundamentally employs a channel-independent modeling approach (parameter-shared) and linear-based methods, which limit its performance on high-dimensional datasets. This is because such scenarios require non-linear capabilities to remember different patterns of multiple channels, or a separate linear layer for each channel (non-parameter-shared) to model each channel's patterns separately [1]. *In contrast, CycleNet’s RCF technique is a fully channel-independent modeling scheme (non-parameter-shared)*, meaning it models each channel's periodic pattern separately. In this case, even with Linear as the backbone, it performs better on high-dimensional datasets because it enhances the model's ability to capture different patterns of multiple channels. Therefore, as shown in our comparison results in *Table 1 of the attached PDF*, **our RCF technique overall still outperforms the Sparse technique** (even on the ETT dataset). *We will include full experiments on more datasets in the revised paper.*
[1] Li, Zhe, et al. "Revisiting long-term time series forecasting: An investigation on linear mapping." *arXiv preprint arXiv:2305.10721* (2023).
> Figure 3(f) is surprising, and it is unclear whether it represents a household or an industrial building with specific working hours. In my opinion, it looks like there are only 3 main weekly patterns (the large pattern on the left seems to have ~50 time steps = 2 days) and weekends (one pattern seems to have ~24 time steps = 1 day). Therefore, it could be a factory or industrial building with specific working hours (6 days a week).
Yes, you are correct. This might represent the typical working hours of a user, for example, working on Monday, Wednesday, and Friday, with the other days off. Indeed, this interesting phenomenon further reveals *the potential value of our proposed RCF technique*, as it may be **a superior way to help data engineers analyze patterns in time series data**.
> “Traffic dataset exhibits spatiotemporal characteristics and temporal lag characteristics, where the traffic flow at a certain detection point significantly affects the future values of neighboring detection points.” However, the authors do not explain why this is not an issue for the Solar-Energy dataset, where weather conditions at one location may slowly impact neighboring locations in the future. Can authors comment on that?
The Traffic and Solar-Energy datasets are indeed quite different.