Summary
This work proposes Recurrent Trace Unit (RTU) as a modified variant of the linear recurrent unit (LRU) which has gained some popularity recently as a linear complexity model.
RTU adopts cosine representations of LRU to manipulate two-coupled real-valued hidden states, and introduces non-linearity (while breaking the equivalence to dense linear RNN when non-linearity is introduced in the recurrence).
Like LRU, RTU allows for tractable real-time recurrent learning (RTRL) through diagonal recurrence.
The focus of this work is on evaluating RTU-RTRL for reinforcement learning (RL) in partially observable environments.
The main experiments are conducted on two partially observable variants of six MuJoCo environments for general evaluation; in addition, one MuJoCo environment (Reacher) and five POPGym environments are used as memory tasks. Positive results for RTU are consistently shown.
Strengths
* Evaluating variants of LRU using RTRL *for reinforcement learning* is novel and interesting.
* Beyond the focus on the RL applications, several interesting details about LRU are discussed while developing RTU (Sec 3.2 and 3.4), which should be of interest to people interested in LRU in general.
* Experiments are conducted on several relevant environments.
Overall, I'm supportive of acceptance, provided that the authors will address the main issues described below.
Weaknesses
**One major issue is the repeated claims about outperforming "Transformers" while no such experiment is provided, certainly not in the main text (not even in the appendix as far as I can tell).** See:
- Abstract Line 11, "RTUs significantly outperform GRUs and Transformers"
- Line 329: "We also included a GPT2-transformer baseline"
- Line 330: "We provide the results for GPT2 in Appendix G."
- Conclusion: Line 356: "performed better than the more computationally intensive GRUs and Transformers"
I could not find the Transformer/GPT2 results even in the indicated Appendix G, Figures 21 or 22 either.
Given all these emphases on this claim, I had expected to see such results in the main text, e.g., in the same style as Figure 4 and 6.
I initially considered putting 1 ("incorrect statements") to encourage the authors to fix this immediately, but in the end, I decided to put the score I would give disregarding any mentions to Transformers. Regarding Transformers, please also check the related comment in the "Questions" field below.
**There are also some clarity issues:**
* Clearer explanations to explain the gap between RTU and LRU are expected.
In Figure 1, some explanations are needed to help the readers understand why there is such a big gap between LRU and RTU when everything is equal except the architecture. Is there anything specific to RTRL? or do you observe similar trends when T-BPTT is used for both models?
Similarly, some explanations should be provided to explain why Online LTU largely underperform RTU models in Figures 4, 5, and 6.
The only related comment I could find is Line 209: *"We found small choices in our implementation for LRU did not always behave as expected, partially due to how auto-differentiation is implemented in packages for complex numbers"*
So is LRU's problem just an implementation issue? Please clarify.
* I find Figure 2 misleading as they mix model architectures and learning algorithms within the same comparison, i.e., they compare LRU-TBPTT with RTU-RTRL.
Instead, the comparison should be between LRU-TBPTT vs. RTU-TBPTT vs. GRU-TBPTT, and LRU-RTRL vs. RTU-RTRL separately. The statement *"LRU and GRU with T-TBTT is not competitive with RTUs"* (caption Figure 2) is true but does not allow us to conclude on the superiority of RTU over LRU since two different learning algorithms are used. I acknowledge that good results are sufficiently shown later in Figures 4, 5 and 6, but Figure 2 alone is not informative.
**Some of the experimental designs are not convincing:**
* (Related to the point above) I find the experimental setting of Sec 4.2/Figure 2 under "resources constraints" too artificial (therefore not particularly useful). Does the chosen "computational budget of 15000 FLOPs" (Line 237) correspond to something intuitive/useful? How does the memory requirement differ between RTU-RTRL and RTU-TBPTT for different values of T?
Questions
Most of the questions have already been asked above. These are comments and suggestions.
* Tractable RTRL with a diagonal recurrent matrix dates back to [R1] [R2] at least, which should be cited.
[R1] Gori et al. IJCNN 1989. BPS: A learning algorithm for capturing the dynamic nature of speech.
[R2] Mozer. Complex Systems 1989. A focused backpropagation algorithm for temporal pattern recognition.
* The authors' view on Transformers for POMDPs (the second paragraph of the introduction; starting at Line 20) is restricted as it lacks discussion about the "linear" variants of Transformers that are stateful and permit a "recursive" formula just like RNNs.
There are several prior works evaluating [R3] [R4] [R5] and discussing [R6] such models in the context of reinforcement learning.
[R3] Irie et al. NeurIPS 2021. Going Beyond Linear Transformers with Recurrent Fast Weight Programmers.
[R4] Irie et al. ICML 2022. A Modern Self-Referential Weight Matrix That Learns to Modify Itself.
[R5] Pramanik et al. arXiv 2023. Recurrent Linear Transformers.
[R6] Lu et al. ICML 2024. Rethinking Transformers in Solving POMDPs.
* In the equation just below Line 118 (sec 3.1), *"f("* is a typo at this stage (the non-linearity is not introduced yet).
* Regarding the non-linearity "f", for the tractable RTRL to hold, "f" has to be a *purely* element-wise function. For example, softmax or layernorm would not work there (as they introduce interactions between recurrent units); I know nobody would use softmax or layernorm as a recurrent non-linearity in practice, but it might make sense to point out that there is a condition on "f", in the strict mathematical sense.
* It is unfortunate that no further architectural advances have been integrated and evaluated. Based on [11], gating can be made compatible with RTRL, and a recent model that is closely related to LRU, "Mamba", also puts back gating to linear recurrence. So some gating could have been a natural extension too.
* The proposed RTU is not specific to RL. I'm wondering if the authors considered applying it to other supervised learning applications.
Limitations
Comments are already provided above.