- Rating
- 2
- Confidence
- 4
- Informativeness
- 2
- Presentation
- 2
- Soundness
- 2
Read review
Paper summary
PRISM addresses cross-session drift in streaming intracortical motor decoding. It builds a cached, reference-conditioned channel interface from unlabeled support, followed by communicating channel recurrences, population aggregation and complex recurrent memory. Its stated contributions are this computational organization, the relational interface with channel history before final aggregation, and an empirical accuracy–resource characterization. FALCON results, 16-date Indy experiments and resource measurements support a useful complete system; the incremental benefit of relational processing and the preferred placement of recurrence are less clearly established.
Critical strengths
S1. Useful performance at modest streaming cost. PRISM achieves competitive cross-session decoding performance on FALCON with lower reported latency than the displayed few-shot unsupervised comparators. Its low computational cost and compact recurrent state support its practical value for streaming motor decoding.
S2. Useful controlled observations. Controlled experiments demonstrate the benefits of target-session calibration and channel recurrence within PRISM.
Critical weaknesses
W1. The motivation for the specific design and its incremental contribution are insufficiently distinguished from prior work. The cross-session decoding problem and the contributions are listed, but it remains unclear why the proposed interface and recurrence organization are preferable to existing unsupervised adaptation and temporal/population modeling approaches. SPINT [1] already derives unit identities from unlabeled support and processes causal per-unit histories; EIT [2] models individual temporal dynamics before population interaction. These connections warrant a clearer account of what its particular interface and organization add. The full-model comparison with SPINT does not isolate an advantage over IDEncoder.
The ablations leave this distinction unresolved. NoTargetCalibration retains the learned interface and 108-second replay while substituting source-fixed normalization/support quantities , so its performance drop does not isolate relational matching. Table 6's existing StandardizationOnly comparison uses one checkpoint per model and incompletely specifies the bypass. Although the 51-feature construction is described, the existing controls do not isolate the incremental contribution of its relational feature groups. A clearly defined, replicated StandardizationOnly comparison is the smallest useful check; more targeted feature-group or IDEncoder-style controls would be informative.
POSSM [3] is also a relevant, cited recurrent decoder, but is absent from the measured comparisons. The current ablation removes channel-level recurrent memory rather than relocating it, so it does not isolate the effect of recurrence placement. A POSSM-style or another matched aggregate-first recurrent baseline would address that distinction. The existing evidence therefore supports the usefulness of channel recurrence within PRISM, but does not establish an advantage of the proposed placement.
W2. The methodology and supporting figures do not explain the contribution clearly. Many equations and variables are introduced without a sufficiently clear account connecting the support features, learned encoder, channel map and recurrent blocks to source training and target-session inference. Figure 2 does not adequately explain these operations or which quantities are learned, computed from support, cached or updated per bin. A revised diagram and a short training/calibration/inference walkthrough would make the design and its claimed contribution easier to assess.
The supplementary presentation is also unfinished. S1 includes the instruction, “The caption should identify the displayed recording or date, the query interval, the velocity components, and the meanings of all lines, markers, and shaded regions.” S2/S4 contain similar editorial directions; S3's plot and caption describe different tasks/context settings. Together with the unclear methodological exposition, they weaken confidence in assessing the mechanism claims; caption cleanup alone would not resolve the main scientific concern.
References
[1] Trung Le et al. SPINT: Spatial Permutation-Invariant Neural Transformer for Consistent Intracortical Motor Decoding. NeurIPS, 2025.
[2] Ran Liu et al. Seeing the forest and the tree: Building representations of both individual and collective dynamics with transformers. NeurIPS, 2022.
[3] Avery Hee-Woon Ryoo et al. Generalizable, real-time neural decoding with hybrid state-space models. NeurIPS, 2025.
Questions for authors
Q1. What motivated the selection of the 51 support features, and what evidence supports the contribution of the relational feature groups? What distinctive capability does the shared encoder/reference interface offer compared with SPINT’s IDEncoder, and what evidence supports it? Please clarify whether relational feature engineering supplies the claimed distinctive benefit.
Q2. Beyond the Full-versus-NoTargetCalibration bundle comparison, what evidence distinguishes the contribution of the learned interface from target-session normalization? In particular, what exactly does StandardizationOnly disable? Table 6 shows nearly identical clean performance but positive mean gains for Full under persistent channel loss. How do the authors interpret this difference, and does the robustness benefit persist across training seeds?
Q3. Can the placement claim be supported by a POSSM-style or another comparable-capacity aggregate-first recurrent baseline using the same interface, supervision and calibration access, with resource differences reported? The current ablation removes channel-level recurrent memory rather than relocating it, so it does not isolate recurrence placement. Alternatively, is the intended claim only that channel recurrence helps this architecture?
Q4. What explains PRISM's latency advantage, and how does it compare with one suitable streaming decoder, such as POSSM or a Mamba-based decoder, with accuracy, capacity and context differences reported? Please identify the exact implementation used for timing and clarify what evidence attributes the advantage to the proposed organization rather than implementation or model-size differences.
Q5. The supplied local trainer differs from Appendices A.1, A.4 and A.5 in source-reference selection, the training objective, learning-rate schedule and backpropagation procedure, prefix-state handling during training, and checkpoint selection. For example, train.py selects the first training session as the reference rather than applying Eq. 16, and saves the final model without evaluating the allocated validation sessions. Please identify which implementation and configurations generated the reported results and explain their correspondence to the supplied package.
Dear Reviewers,
Please take a moment to review the authors’ rebuttal, assess whether your concerns have been adequately addressed, and actively participate in the discussion. Please update your assessment if needed. Thank you for your time and effort!