LAYA: Layer-wise Attention Aggregation for Interpretable Depth-Aware Neural Networks

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:2511.12723v2 Announce Type: replace Abstract: Deep neural networks typically rely on the representation produced by their final hidden layer to make predictions, implicitly assuming that this single vector fully captures the semantics encoded across all preceding transformations. However, intermediate layers contain rich and complementary information---ranging from low-level patterns to high-level abstractions---that is often discarded when the decision head depends solely on the last representation. This paper revisits the role of the output layer and introduces LAYA (Layer-wise Attention Aggregator), a novel output head that dynamically aggregates internal representations through attention. Instead of projecting only the deepest embedding, LAYA learns input-conditioned attention weights over layer-wise features, yielding an interpretable and architecture-agnostic mechanism for synthesizing predictions. Beyond improving feature aggregation, the learned attention coefficients provide intrinsic layer-attribution scores that explicitly quantify the contribution of each representation to the final decision, without requiring external post-hoc explanation methods. Experiments on image classification datasets show that LAYA achieves competitive predictive performance while producing meaningful depth-aware explanations. Furthermore, quantitative and qualitative interpretability analyses demonstrate that LAYA's attention scores closely reflect the actual contribution of individual layers, revealing structured, task-dependent patterns of depth utilization while providing …

Vollständiger Originalartikel ↗

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