A Unified Geometric Framework for Developmental Analysis of Spatial Transcriptomic Data

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:2608.15306v1 Announce Type: cross Abstract: High-throughput single-cell and spatial transcriptomic technologies provide high-resolution snapshots of heterogeneous cellular states, but their destructive nature prevents repeated measurements of the same cells over time. Consequently, temporal and spatial dynamics must be inferred from independently sampled, unaligned cell populations, making it challenging to reconstruct developmental trajectories. Optimal transport (OT) offers a geometric framework for aligning cell populations and inferring developmental trajectories, but many existing approaches focus on modeling the evolution of distributions of cells in gene expression space rather than the relational structure encoded by gene expression networks. To address this limitation, we introduce a geometric framework for analyzing the spatiotemporal evolution of gene expression networks through embeddings in Gromov--Wasserstein (GW) space. By representing each developmental stage as a graph combining gene expression and spatial proximity, our approach enables comparisons of network structure across time, continuous interpolation between developmental stages via GW geodesics, and quantification of network-level changes using Ollivier-Ricci curvature. We evaluate our framework on a spatiotemporal transcriptomic \textit{Drosophila} dataset and show that GW geodesic interpolations reproduce main trends in curvature dynamics observed in empirical gene expression networks. Agreement with higher-order Co-Optimal Transport (COOT) distances, which jointly represent spatial and …

Vollständiger Originalartikel ↗

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