- Rating
- 1
- Confidence
- 4
- Informativeness
- 1
- Presentation
- 2
- Soundness
- 1
Read review
Paper summary
Summary
In this paper, the authors proposed RobustNCL, which addresses the vulnerability of the Neuromorphic Continual Learning (NCL) framework to transient DRAM bit-flips. The paper proposes a lightweight detect-and-cure strategy that identifies anomalous weights using the clean weight distribution and replaces them with zero, the minimum/maximum boundary value, or the most probable synaptic weight. To accommodate the evolving model states in continual learning, the curing statistics are updated after each task and evaluated using both task-specific subnetwork and memory replay approaches. Experiments based on a spiking VGG-9 model on Split MNIST, Split Fashion-MNIST, Split CIFAR-10, and Split CIFAR-100 show that RobustNCL can maintain accuracy close to the fault-free baseline with relatively small reported latency, memory, and energy overheads.
Critical strengths
Strengths
- The proposed mechanism is simple and notably enhances the fault tolerance of SNNs.
- The detailed problems mentioned in subsection 3.2 are somewhat clear.
Critical weaknesses
Weaknesses
- I think this paper fits well with DAC or DATE. Although the proposed mechanism is practical in hardware aspects, it does not show interesting interactions between faults and learning. If the authors state the relations between hardware faults and learning aspects of CL, I can slightly change my opinion about this paper. For example, the authors should investigate how hardware faults affect CL and degrade SNNs' performance. This is because this venue is deeply related to learning methods of neural networks and other machine learning approaches.
- The detailed problems caused by hardware faults, such as bit flips, are not novel. Actually, the problems mentioned in this paper are already investigated by existing studies [1, 2, 3].
- Although the authors target hardware faults in NCL, they only provide experimental results based on software. I think they would demonstrate that their mechanism works well in a software environment for hardware simulations, such as Intel Lava. However, they do not even show these kinds of results. This critical problem severely damages the paper's reliability. For further improvement, I strongly recommend that the authors use real devices like BrainScaleS-2 or hardware simulation environments like Intel Lava to demonstrate that their mechanism is effective with hardware devices.
- Authors should use more types of network structures. They use only the VGG-9 structure for software simulations. They should use at least ResNet structures to show the effectiveness of their mechanism. This is because there are large SNN structures that can operate on neuromorphic devices, such as Intel Loihi and BrainChip Akida.
- The authors do not compare their mechanism to conventional approaches to enhance fault tolerance of hardware-based NCL, which is a significant weakness of this paper.
[1] Rachmad Vidya Wicaksana Putra, Muhammad Abdullah Hanif, and Muhammad Shafique, "SoftSNN: Low-Cost Fault Tolerance for Spiking Neural Network Accelerators under Soft Errors," in Proceedings of the 59th ACM/IEEE Design Automation Conference (DAC), pp. 151–156, 2022.
[2] Rachmad Vidya Wicaksana Putra, Muhammad Abdullah Hanif, and Muhammad Shafique, "RescueSNN: Enabling Reliable Executions on Spiking Neural Network Accelerators under Permanent Faults," Frontiers in Neuroscience, vol. 17, Art. no. 1159440, 2023.
[3] Thai-Hoang Nguyen, Muhammad Imran, Jaehyuk Choi, and Joon-Sung Yang, "CRAFT: Criticality-Aware Fault-Tolerance Enhancement Techniques for Emerging Memories-Based Deep Neural Networks," IEEE Transactions on Computer-Aided Design of Integrated Circuits and Systems, vol. 42, no. 10, pp. 3289–3300, 2023.
Questions for authors
Questions
- Could you please explain why the characteristics of SNNs make them suitable for CL? For example, why are their event-driven and sparse spiking characteristics useful for CL? Although the authors cite some references, I recommend that they clearly state the reasons in the introduction in one or two sentences.
- In my opinion, DRAM is used to implement ANNs on real hardware devices. Furthermore, hardware faults occur less frequently in DRAM than in RRAM (memristors) because DRAM is more stable. However, the authors consider DRAM for hardware implementation of SNNs. Do you have any clear reasons to consider DRAM?
- During CL, synaptic weights are updated, which means that they can be affected by errors or faults caused by abnormal updates. Do you consider them? I think errors or faults during weight updates are also considerable [1].
[1] Hyun-Jong Lee and Jae-Han Lim, "Practical Mechanism for Fault-Tolerant Spiking Neural Networks via Simple Input Control Based on Learnable Fragmentation," in Proceedings of the 43rd International Conference on Machine Learning (ICML), PMLR, vol. 306, pp. 64616–64653, 2026.
5 comments
Response to Reviewer EUq2 [Weakness-2]
We would like to thank you for your valuable comments and constructive feedback. We have considered each comment and provide responses below.
Response to [Weakness-2]: "The detailed problems caused by hardware faults, such as bit flips, are not novel."
The transient faults problem is not new in the research community, but studying the impact of transient faults in the continual learning domain (especially in neuromorphic computing) is novel. Furthermore, the unpredictable nature of transient faults, which can occur at anytime, at any fault rate, and with different possible fault map each time the faults appear during the operational time of the system, combined with the dynamic nature of model (weight) updates in continual learning scenario, make the position of our study unique and relevant to the recent advances of AI systems toward smart and runtime adaptation.
The reference works mentioned have limitations that make them unsuitable for nauromorphic continual learning (NCL) scenario. Following are the reasons.
[1] Rachmad Vidya Wicaksana Putra, Muhammad Abdullah Hanif, and Muhammad Shafique, "SoftSNN: Low-Cost Fault Tolerance for Spiking Neural Network Accelerators under Soft Errors," in Proceedings of the 59th ACM/IEEE Design Automation Conference (DAC), pp. 151–156, 2022.
SoftSNN aims to mitigate transient faults in the compute engine of SNN accelerator that performs SNN inference, hence it employs fixed weight distributions to mitigate the transient faults in the model weights. Therefore, it does not have mechanisms that accommodate NCL training and dynamic ranges of weight distributions for transient fault mitigation.
[2] Rachmad Vidya Wicaksana Putra, Muhammad Abdullah Hanif, and Muhammad Shafique, "RescueSNN: Enabling Reliable Executions on Spiking Neural Network Accelerators under Permanent Faults," Frontiers in Neuroscience, vol. 17, Art. no. 1159440, 2023.
RescueSNN aims to mitigate permanent faults in the compute engine of SNN accelerator through fault-aware mapping that leverages a fixed fault map before deployments. Therefore, it does not have mechanisms that accommodate the dynamic nature of transient faults which may appear with a different fault rate and a different fault map each time high-energy particle strikes the DRAM main memory during runtime operations.
[3] Thai-Hoang Nguyen, Muhammad Imran, Jaehyuk Choi, and Joon-Sung Yang, "CRAFT: Criticality-Aware Fault-Tolerance Enhancement Techniques for Emerging Memories-Based Deep Neural Networks," IEEE Transactions on Computer-Aided Design of Integrated Circuits and Systems, vol. 42, no. 10, pp. 3289–3300, 2023.
CRAFT aims to mitigate stuck-at faults (which are manifestation of permanent faults) on emerging memories for deep neural networks, hence it leverages a fixed fault map before deployments. Consequently, it also does not have mechanisms that accommodate the dynamic nature of transient faults which may appear with a different fault rate and a different fault map each time high-energy particle strikes the DRAM main memory during runtime operations.
Response to Reviewer EUq2 [Weakness-3 and Weakness-4]
Response to [Weakness-3]: "Although the authors target hardware faults in NCL, they only provide experimental results based on software."
We agree that hardware-level evaluation is important, but performing transient fault injection in real neuromorphic compute platforms may damage the hardware, which are typically very costly and have limited accessibility. Therefore, the purpose of software-level experiments is to enable us perform a comprehensive design space exploration (DSE) that considers a wide-range of different possible design scenarios that may happen in the real-world environments/deployments without damaging the actual hardware. Additionally, a comprehensive DSE also provides near-accurate experimental results, from which we can draw insightful key observations.
The transient faults may happen at anytime and at any fault rate. For instance, a fault rate of in DDR3-1600 2Gb DRAM chip means faulty bits at the same time, and they may happen anytime (e.g., multiple times in one hour) in the operational lifetime of the system. Therefore, in our RobustNCL development, we consider a challenging transient fault model with a comprehensive DSE scenarios.
- First: Transient faults are injected when (1) the clean weights of pre-trained model are deployed and stored in the DRAM main memory for the first time, and when (2) the model weights are updated after performing NCL training at runtime. Therefore, the model weights are always exposed and affected by faults.
- Second: We explore a wide range of fault rates (i.e., between $ 1 \times 10^{-7} - 5 \times 10^{-4}$). These challenging conditions are explored in our work to ensure that our RobustNCL methodology can perform reliably in diverse operational environments. Therefore, we develop RobustNCL to always monitor the weights accessed from the DRAM main memory of the system hardware and curing them before performing inference or NCL training.
Response to [Weakness-4]: "Authors should use more types of network structures."
We agree that using more networks in the evaluation will strengthen the claim. However, our proposed RobustNCL framework is developed without any constraints of network structures, thereby making it applicable to any network structures that are used for performing continual learning process. Specifically, RobustNCL aims to monitor weight values accessed from DRAM main memory and then cure (replace) them if anoumalous signatures are detected. Therefore, it is applicable to any network architectures/strcutures.
Response to Reviewer EUq2 [Weakness-1]
We would like to thank you for your valuable comments and constructive feedback. We have considered each comment and provide responses below.
Response to [Weakness-1]: "it does not show interesting interactions between faults and learning"
In Section 5 "Results and Discussion", we show that the baseline neuromorphic continual leaning (NCL) suffer from significant performance (accuracy) degradation when NCL training process is performed in the presence of transient faults in the main memory (i.e., DRAM).
The same results are shown in the following tables. Each dataset includes its lowest and highest tested fault rates.
The first table shows results for task-specific subnetworks (Subnet).
The second table shows results for memory replay (MR).
On all four datasets, accuracy without protection falls as the fault rate increases. Our RobustNCL maintains much higher accuracy at the higher fault rates. These results show how faults reduce performance during continual learning and how RobustNCL reduces this loss.
This is interesting and important finding that, even when continual learning (CL) process updates the model weights when learning new tasks, it does not make the model automatically become more robust and adapt better to the faults. Moreover, the transient faults may happen at anytime, at any fault rate, and with a different fault map each time high-energy particle strikes the DRAM main memory during runtime operations, thereby making it even more challenging and difficult to make the model become robust against transient faults.