ERP-XTTN: Interpretable Prototype-Guided Cross-Attention for Cross-Subject ERP Classification

Sicherheitsmeldung mit Schweregrad noch nicht bewertet. Technische Details im Tab „Originaltext“; empfohlene Schritte in der Checkliste.

Originaltext der Quelle (nicht übersetzt) – die deutsche Zusammenfassung findest du im Tab „Kurzfassung".

arXiv:2606.02939v2 Announce Type: replace Abstract: Interpretable brain-computer interface classifiers that generalize across subjects without calibration remain an open challenge. We evaluated whether prototype-based cross-attention can provide competitive, inherently interpretable ERP classification across paradigms under deployment-compatible conditions. We propose ERP-XTTN (ERP Cross-Attention), a cross-attention architecture that routes input EEG peaks to fixed difference-wave prototypes via query-key-only cross-attention with no value projection. Classification is based directly on prototype similarity and a separate measure of component amplitude, so that prototype content contributes to every decision by construction. Prototypes are derived automatically from prominent extrema in the training-fold grand-average difference wave. We evaluated across three public sources (BNCI Horizon 2020, HRI Cursor, and ERP CORE) encompassing eight ERP components (ERN, LRP, ErrP, N170, P300, N2pc, MMN, N400). Evaluations used LOSO cross-validation with causal filtering at a three-channel montage, compared against EEGNet, EEG-Deformer, EPMN, and xDAWN with Riemannian geometry. The mean performance gap between the best baseline and ERP-XTTN was 0.025 AUROC. Prototype interventions confirmed that decisions depend on prototype content rather than on the routing attention pattern alone. False positives morphologically resembled true positives more than true negatives did, so classification errors are neurophysiologically explicable. ERP-XTTN generalizes across diverse ERP morphologies …

Vollständiger Originalartikel ↗

• Betroffenheit im eigenen Stack prüfen: Versionen/Komponenten abgleichen.
• Originalquelle / Hersteller-Advisory lesen: https://arxiv.org/abs/2606.02939
• Verfügbaren Patch oder Workaround einspielen und dokumentieren.