Papers › PRAGA: Prototype-aware Graph Adaptive Aggregation for Spatial Multi-modal Omics Analysis

PRAGA: Prototype-aware Graph Adaptive Aggregation for Spatial Multi-modal Omics Analysis

19 Sep 2024arXiv:2409.12728archive 2025-07-28

Xinlei Huang, Zhiqi Ma, Dian Meng, Yanran Liu, Shiwei Ruan, Qingqiang Sun, Xubin Zheng, Ziyue Qiao

Spatial multi-modal omics technology, highlighted by Nature Methods as an advanced biological technique in 2023, plays a critical role in resolving biological regulatory processes with spatial context. Recently, graph neural networks based on K-nearest neighbor (KNN) graphs have gained prominence in spatial multi-modal omics methods due to their ability to model semantic relations between sequencing spots. However, the fixed KNN graph fails to capture the latent semantic relations hidden by the inevitable data perturbations during the biological sequencing process, resulting in the loss of semantic information. In addition, the common lack of spot annotation and class number priors in practice further hinders the optimization of spatial multi-modal omics models. Here, we propose a novel spatial multi-modal omics resolved framework, termed PRototype-Aware Graph Adaptative Aggregation for Spatial Multi-modal Omics Analysis (PRAGA). PRAGA constructs a dynamic graph to capture latent semantic relations and comprehensively integrate spatial information and feature semantics. The learnable graph structure can also denoise perturbations by learning cross-modal knowledge. Moreover, a dynamic prototype contrastive learning is proposed based on the dynamic adaptability of Bayesian Gaussian Mixture Models to optimize the multi-modal omics representations for unknown biological priors. Quantitative and qualitative experiments on simulated and real datasets with 7 competing methods demonstrate the superior performance of PRAGA. Code is available at https://github.com/Xubin-s-Lab/PRAGA.

PaperPDFCodeCode Syntology ran

In Syntology View this paper on Syntology, its page in Syntology's graph. That page adds which of its functions are also present in other papers' code Syntology holds, with dates, and its dated run record as JSON and a README badge. It also lists the repositories linked to the paper, the abstract and the calls for agents.

Open this paper in Syntology's Atlas, the map of the papers in Syntology's graph and their citations.

For agents, on Syntology's MCP service (how to connect):

Code

Syntology 11 code samples harvested from 1 repository linked to this paper: 8 ran (of which 0 constructed an object rather than computing a result; 6 with no instrument failure: 1 honoured, 0 violated, 5 with no contract checked; 2 where Syntology's instrument failed) · 3 unverified. Where Syntology's instrument failed: 2 where our contract draft was wrong; failures of Syntology's instrument, not of the code.

By repository: official repository: 11 samples from 1 repository, 8 ran (6 with no instrument failure; 2 where Syntology's instrument failed). The run record, sample by sample. “Ran” means executed on a synthesized input, not that the code is correct or reproduces the paper.

Levels written on 2026-09-24 (UTC): the dates Syntology's graph wrote each sample's verification level, not when the code executed.

xubin-s-lab/praga officialmentioned in paperpytorchAGPL-3.0Syntology: 11 samples, 8 ran (2 instrument-failed) · 3 unverified report

Repository list and official/mentioned flags are the archive's, frozen 2025-07-28. Reachability, where shown, is from one Syntology probe window (2026-09-16 to 2026-09-18); repositories not probed show nothing. GitHub stars are not tracked.

Code Syntology ran Syntology

11 samples harvested: 8 ran (of which 0 constructed an object rather than computing a result; 6 with no instrument failure: 1 honoured, 0 violated, 5 with no contract checked; 2 where Syntology's instrument failed) · 3 unverified. “Where Syntology's instrument failed” counts failures of Syntology's instrument, not of the code. Syntology's record for this page last changed ; when this build read Syntology's graph is in the build record. That date is not when the samples ran.

1ran · honoured contract
2ran · our draft was wrong
5ran
3unverified

Licence: 11 of the 11 samples are pointer only, meaning Syntology does not serve that copy's text. This page shows no code text for any sample; each one links to its file in the repository.

Harvested from xubin-s-lab/praga. “Ran” means the sample executed on a synthesized input. It does not mean the output is correct, and nothing here reproduces the paper's results. A line beginning “fixture:” under a sample that ran gives the arguments Syntology's fixture called the sample with, each as name:type/rank/element kind (? where none was recorded), and the type of what the fixture's run returned, exactly as the harness recorded them; the arguments and the returned type were recorded by two separate runs of the same fixture. No output value is shown, and a returned type says nothing about whether the output was right. “Level recorded” gives the UTC date when Syntology's graph wrote the sample's verification level, not when the code executed; where the level was written before Syntology's graph kept that date, the row says “level recorded, date not recorded”. “Honoured” and “violated” refer to a contract Syntology drafted from the code itself. “Our draft was wrong” and “the contract check could not run” are failures of Syntology's instrument, not of the code: the sample ran on Syntology's synthesized input, and then the drafted contract did not describe it, or the check itself raised an error (RAISES), lacked a dependency (DEP_MISSING) or ran out of time (TIMEOUT); hover the label for which. A metamorphic tier, where shown, is evidence of the output's shape, not that the sample implements the method.

Each sample ends with its code_sha256. A sample's code_sha256 is Syntology's identity for that exact code. It is printed in full (16 hexadecimal characters for every sample in this build), and get_code(code_sha256="…") takes it exactly as printed. An agent calls it on Syntology's MCP service (how to connect); click an identity to copy that call.

Repository labels, per sample. official repository: The archive marks this repository official for the paper. named in the paper: The archive records that the paper mentions this repository; it is not marked official. community (archive-listed): In the archive's code links for this paper, not marked official and not recorded as mentioned in the paper. found in paper text by Syntology: Syntology found this repository in the paper's own text; whether it is the authors' implementation is not asserted. community: Not in the archive's code links for this paper; a community repository Syntology harvested. Samples are grouped by repository: a repository marked official first, then by how directly the repository is tied to the paper, then in the archive's order; never by how many ran. Licence labels name the repository's licence as recorded at harvest. “Pointer only” means Syntology does not serve that copy's text, for one of six reasons: no licence file was found; the licence was not identified; the licence is recorded as permissive but that copy's record is not marked cleared; the licence is outside the permissive list Syntology serves text under (MIT, Apache-2.0, BSD and similar); this paper's copy was not located, so its licence is not recorded; or this paper's copy is cleared, but the stored copy of the same code that Syntology serves is not. Some licences outside that list permit redistribution, such as WTFPL, and GPL-3.0 under its conditions; they are simply not on the list. Hover a licence label for the reason. File links open the file on GitHub at the default branch, which may have changed since the harvest.

A function or class name links to its page when the name occurs in the harvested code of at least 5 papers; the name is a string, not an identity. A census tag appears when Syntology's census ran implementations with that name on one shared input per bucket: it gives how many were compared, from how many papers, and how many distinct outputs they produced, and names this sample's bucket when this sample was one of them.

xubin-s-lab/praga official repository 11 samples, 8 ran (2 instrument-failed) · 3 unverified
clr_normalize_each_cell PRAGA/preprocess.py ran · our draft was wrong AGPL-3.0 (copyleft) · pointer only · 26c85baaa84ab990 · report fixture: signature adata:MinimalAdata/0/?, inplace:bool/0/bool · returned MinimalAdata · level recorded 2026-09-24
construct_neighbor_graph PRAGA/preprocess.py ran AGPL-3.0 (copyleft) · pointer only · b00496f9ea926325 · report fixture: signature adata_omics1:MockAnnData/0/?, adata_omics2:MockAnnData/0/?, datatype:str/0/str, n_neighbors:int/0/int, Arg:MockArg/0/? · returned dict · level recorded 2026-09-24
get_rs metric.py ran · our draft was wrong AGPL-3.0 (copyleft) · pointer only · 02117d09b11d48b5 · report fixture: signature x:NoneType/0/? · returned module · level recorded 2026-09-24
get_sub_assign_with_one_cluster clustering_utils.py ran AGPL-3.0 (copyleft) · pointer only · dff3b6e32dbd1fd5 · report fixture: signature feat:Tensor/2/float, labels:Tensor/1/int, k:int/0/int, prior:MockPrior/0/? · returned tuple · level recorded 2026-09-24
mean_average_precision in 15 papers metric.py ran AGPL-3.0 (copyleft) · pointer only · 9557c1988e29c353 · report fixture: signature x:ndarray/2/float, y:ndarray/1/int, neighbor_frac:float/0/float · returned float · level recorded 2026-09-24
pairwise_distance in 55 papers
census: 6 implementations from 7 papers, 5 distinct outputs across 3 buckets, one shared input per bucket
clustering_utils.py ran AGPL-3.0 (copyleft) · pointer only · c28231e92b528a79 · report fixture: signature data1:Tensor/2/float, data2:Tensor/2/float, batch_size:NoneType/0/? · returned Tensor · level recorded 2026-09-24
pca in 16 papers PRAGA/preprocess.py ran AGPL-3.0 (copyleft) · pointer only · 434c64e6c74854b9 · report fixture: signature adata:AnnDataStandIn/0/?, use_reps:str/0/str, n_comps:int/0/int · returned ndarray · level recorded 2026-09-24
read_list_from_file cal_matrics.py ran · honoured contract AGPL-3.0 (copyleft) · pointer only · 5b67b0cdfe63acf3 · report fixture: signature path:str/0/str · returned list · level recorded 2026-09-24
cluster_acc in 33 papers clustering_utils.py unverified AGPL-3.0 (copyleft) · pointer only · b6de204a76f878fe · report
construct_neighbor_graph PRAGA/preprocess_3M.py unverified AGPL-3.0 (copyleft) · pointer only · 9dd543809c490470 · report
mclust_R PRAGA/utils.py unverified AGPL-3.0 (copyleft) · pointer only · b1af9bb9030ff289 · report

Tasks

Contrastive Learning

Results from the paper archive 2025-07-28

No leaderboard rows for this paper in the archive.

Methods

Contrastive Learning

Report a problem or propose a change · a person checks every report against the paper or source before anything changes; decisions are listed on /corrections