Slightly Shift New Classes to Remember Old Classes for Video Class-Incremental Learning
Jian Jiao, Yu Dai, Hefei Mei, Heqian Qiu, Chuanyang Gong, Shiyuan Tang, Xinpeng Hao, Hongliang Li
TL;DR
SNRO tackles catastrophic forgetting in video class-incremental learning under fixed memory by subtly shifting learning toward low-semantic features through Examples Sparse ($ES$) and preventing overfitting via Early Break ($EB$). It down-samples old-class videos to create larger memory sets and uses Frame Alignment to preserve compatibility with the network input, while EB stops training early to avoid over-optimizing for new classes. Across UCF101, HMDB51, and UESTC-MMEA-CL with the same memory budget, SNRO delivers higher final-task accuracy and lower forgetting than prior memory-replay approaches, demonstrating memory-efficient retention of old classes in sequential video recognition. Overall, SNRO provides a practical strategy to balance old and new class knowledge with limited storage, improving long-term performance in video CLASS-incremental learning.
Abstract
Recent video class-incremental learning usually excessively pursues the accuracy of the newly seen classes and relies on memory sets to mitigate catastrophic forgetting of the old classes. However, limited storage only allows storing a few representative videos. So we propose SNRO, which slightly shifts the features of new classes to remember old classes. Specifically, SNRO contains Examples Sparse(ES) and Early Break(EB). ES decimates at a lower sample rate to build memory sets and uses interpolation to align those sparse frames in the future. By this, SNRO stores more examples under the same memory consumption and forces the model to focus on low-semantic features which are harder to be forgotten. EB terminates the training at a small epoch, preventing the model from overstretching into the high-semantic space of the current task. Experiments on UCF101, HMDB51, and UESTC-MMEA-CL datasets show that SNRO performs better than other approaches while consuming the same memory consumption.
