Response to Reviewer WuBX
Thank you for your review comments. We reply to the weak points and answer your questions. For clarity, we have addressed each of your comments individually in the following responses:
**---The paper is in parts poorly written and very hard to follow. It would benefit from substantial language editing. Also, there are some Sentences and sections, e.g. 3rd paragraph of the introduction, whose meaning I do not understand at all.**
We apologize if there was any confusion. However, we have had native English speakers proofread and confirm that there are no problems.
**---The experimental evaluation is kept rather short. While it does seem to confirm the theoretical findings, there is no clear description of the experiments (e.g. the utilized model architecture and training setup), and no source code, which prohibits reproduction of the results.
---What model architecture and training setup was used for the experiments. As it, they are not reproducible by others.**
The details of the model used and the training setup can be found in Appendix C, and the source code is available in the Supplementary material. It is important to note that all setups were consistent with the experiments conducted by Xiao et al. [2022].
**---The prior work and related concepts upon which the contribution of the authors build is not explained very well. Half of the assumptions and derivations are to be found in other papers, making it almost impossible to fully grasp the paper as a stand alone. It appears to be follow-up work by the authors of previous work, hence the authors don’t seem to find it necessary to fully explain the background concepts**
The concept of this study is fully explained in Section 4.1. On the other hand, due to page limitations, it is only possible to include some reasoning in the main text. The detailed is provided in Appendix A.
SAF offers memory reduction by eliminating the need to calculate membrane potentials during training, as well as halving the time required for weight calculation during forward propagation. In our experiments, SAF achieved a significant reduction of 30\% in memory usage compared to OTTT. Similarly, the training time was also reduced by the same percentage, at least. These results demonstrate substantial differences between the two methods and highlight the significance of SAF's contributions. Moreover, we have established the theoretical consistency of SAF with OTTT and spike representation for both of forward and backward. Based on these contributions, our paper goes beyond being a mere follow-up, and we believe that it is suitable for acceptance by ICLR.
**---It is not clear to me why the approach works for small time steps. As stated in section 3.2 Spike representation assumes a rather large latency (T $\to \inf$) to work. Does that not also apply to SAF? In Fig. 5 you show that firing rates for OTTT and SAF are NOT Identical. Then why do your experiments assume T=6? Where does the averaged spike representation come from in practice?**
There are two reasons why we set $T=6$. First, OTTT's original paper (Xiao et al. [2022]) sets $T=6$. Second, in the case of CIFAR-10, the original paper on spike representation (Meng et al. [2022]) compares the four cases of $T=20,15,10,5$. The results show that the accuracy drop was less than 1\%, and SOTA was achieved at $T=5$. Since SAF-F and OTTT$ _ \rm{A}$ are different at $T=6$, it is unnecessary to increase $T$ to obtain similar results.
It is indeed consistent with SAF-F for spike representation, but not with OTTT$_ \rm{A}$ . Section 5.2 confirms this distinction, highlighting the differences between the two methods. Consequently, the firing rates are expected to differ, which is correct. On the other hand, Section 5.1 describes the results of an experiment that confirms the equivalence between SAF-E and OTTT$ _ \rm{O}$. The figure presented in this section demonstrates the same firing rates. Thanks to your review, we have added explanations to the figure captions in Section 5, improving readability.
**---In Section 3, Spike Representation, what is x for the weighted average input? Not mentioned before**
$x$ is the value of the input data. In the case of CIFAR-10, it is the value of each pixel in the image. This explanation has been added to the main text.