Papers › Multimodal Optimal Transport-based Co-Attention Transformer with Global Structure...
Multimodal Optimal Transport-based Co-Attention Transformer with Global Structure Consistency for Survival Prediction
Yingxue Xu, Hao Chen
Survival prediction is a complicated ordinal regression task that aims to predict the ranking risk of death, which generally benefits from the integration of histology and genomic data. Despite the progress in joint learning from pathology and genomics, existing methods still suffer from challenging issues: 1) Due to the large size of pathological images, it is difficult to effectively represent the gigapixel whole slide images (WSIs). 2) Interactions within tumor microenvironment (TME) in histology are essential for survival analysis. Although current approaches attempt to model these interactions via co-attention between histology and genomic data, they focus on only dense local similarity across modalities, which fails to capture global consistency between potential structures, i.e. TME-related interactions of histology and co-expression of genomic data. To address these challenges, we propose a Multimodal Optimal Transport-based Co-Attention Transformer framework with global structure consistency, in which optimal transport (OT) is applied to match patches of a WSI and genes embeddings for selecting informative patches to represent the gigapixel WSI. More importantly, OT-based co-attention provides a global awareness to effectively capture structural interactions within TME for survival prediction. To overcome high computational complexity of OT, we propose a robust and efficient implementation over micro-batch of WSI patches by approximating the original OT with unbalanced mini-batch OT. Extensive experiments show the superiority of our method on five benchmark datasets compared to the state-of-the-art methods. The code is released.
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):
get_harvested_code_for_paper(arxiv_id="2306.08330")get_code(code_sha256="…")with a sample'scode_sha256from the list belowget_citation_path(paper_1="2306.08330", paper_2="…")with another paper's arXiv id or titleget_concepts_for_paper(arxiv_id="2306.08330")
Code
Syntology 18 code samples harvested from 3 repositories linked to this paper: 10 ran (of which 6 constructed an object rather than computing a result; 7 with no instrument failure: 0 honoured, 0 violated, 7 with no contract checked; 3 where Syntology's instrument failed) · 8 unverified. Where Syntology's instrument failed: 2 where our contract draft was wrong; 1 where the contract check could not run; failures of Syntology's instrument, not of the code.
By repository: official repository: 2 samples from 1 repository, 0 ran (0 with no instrument failure; 0 where Syntology's instrument failed); community (archive-listed): 16 samples from 2 repositories, 10 ran (7 with no instrument failure; 3 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 between 2026-09-22 and 2026-09-24 (UTC): the dates Syntology's graph wrote each sample's verification level, not when the code executed.
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
18 samples harvested: 10 ran (of which 6 constructed an object rather than computing a result; 7 with no instrument failure: 0 honoured, 0 violated, 7 with no contract checked; 3 where Syntology's instrument failed) · 8 unverified. “Where Syntology's instrument failed” counts failures of Syntology's instrument, not of the code. Syntology's record for this page has not changed since , the first build that kept a record date for it; when this build read Syntology's graph is in the build record. That date is not when the samples ran.
Licence: 18 of the 18 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 3 repositories linked to this paper, official or community; the list below is grouped by repository, each group headed by its name and what it is to the paper. “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”. For 1 sample that ran, the graph records a signature this page does not show: for a class the fixture built without calling, the harness called the object with inputs it made up itself, so the recorded signature is the harness's probe, not the fixture's arguments. “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.
82db0b1414d840c6 · report
eee6a34fb548d0d6 · report
7c89241e7e5aff7f · report
fixture: returned SCAF · level recorded 2026-09-22 f2b09ae164d718b5 · report
fixture: signature x:Tensor/4/float · returned Tensor · level recorded 2026-09-24 dbd80cddba6f67f2 · report
fixture: returned Attn_Net_Gated · level recorded 2026-09-22 314f5264c2883265 · report
fixture: returned BilinearFusion · level recorded 2026-09-22 b8a656d552c1f7f0 · report
fixture: returned NLLSurvLoss · level recorded 2026-09-22 d4e04018342ece86 · report
fixture: returned NystromAttention · level recorded 2026-09-22 7cc8eaf772224044 · report
fixture: returned PPEG · level recorded 2026-09-22 98bab5b56a287e4d · report
fixture: signature mu0:Tensor/2/float, logvar0:Tensor/2/float, mu1:Tensor/2/float, logvar1:Tensor/2/float, norm_value:NoneType/0/? · returned Tensor · level recorded 2026-09-22 d9f70b6ed26bc6dc · report
fixture: signature mu0:Tensor/2/float, logvar0:Tensor/2/float, mu1:Tensor/2/float, logvar1:Tensor/2/float, norm_value:int/0/int · returned Tensor · level recorded 2026-09-22 62ede8fe77ab4913 · report
fixture: signature hazards:Tensor/2/float, S:Tensor/2/float, Y:Tensor/1/int, c:Tensor/1/int, alpha:float/0/float, eps:float/0/float · returned Tensor · level recorded 2026-09-22 b3b023b4c6805594 · report
df3c40ea28eee3ff · report
22eac946d1b47bb1 · report
c41f70496ff795c3 · report
763d48b1144254cd · report
4043b3b3f31ca073 · report
Method as code Syntology
What Syntology's graph records as this paper's claimed method, lifted into code: each assembly names its bricks (functions and classes), each with its own role and its own verification level. An assembly is not a check that the code implements the method correctly or reproduces the paper's results. Levels are each brick's own verification level in Syntology's graph (level 0: no recorded run), listed brick by brick and never combined into one level; “ran” means the brick executed on a synthesized input, not that its output is correct, and the instrument figure counts failures of Syntology's instrument, not of the code. Where a model read the code against the paper's claim, each assembly's label verdict is one model's judgement, kept in this page's JSON twin; it is not calibrated, so no card prints it. Siblings are assemblies lifted from this paper in the same batch for the same method: alternative readings kept side by side; none replaces or supersedes another.
3 assemblies on this paper: 3 harvested, 0 generated, listed in 1 groups (siblings lifted in one batch form one group).
3 sibling assemblies for Multimodal Optimal Transport-based Co-Attention Transformer (harvested), lifted in the same batch on 2026-09-09: alternative readings kept side by side; none replaces or supersedes another.
harvested Assembly for Multimodal Optimal Transport-based Co-Attention Transformer (graph method: Multimodal Optimal Transport-based Co-Attention Transformer). 3 bricks; individually on a fixture: 3 ran (of which 1 constructed an object rather than computing a result; 2 with no instrument failure: 0 honoured, 0 violated, 2 with no contract checked; 1 where Syntology's instrument failed) · 0 unverified. The assembly has not been run end-to-end.
one of 3 siblings
- SCAF entry · level 1 · ran ·
7c89241e7e5aff7f - Normalize helper · level 1 · ran · our draft was wrong ·
c3a6b977022957cb - SE_Layer model · level 1 · ran ·
f2b09ae164d718b5
harvested Assembly for Multimodal Optimal Transport-based Co-Attention Transformer (graph method: Multimodal Optimal Transport-based Co-Attention Transformer). 22 bricks; individually on a fixture: 16 ran (of which 9 constructed an object rather than computing a result; 10 with no instrument failure: 0 honoured, 1 violated, 9 with no contract checked; 6 where Syntology's instrument failed) · 6 unverified. The assembly has not been run end-to-end.
one of 3 siblings
- Robust_MCAT entry · level 0 · unverified ·
df3c40ea28eee3ff - Attn_Net_Gated helper · level 1 · ran ·
dbd80cddba6f67f2 - BilinearFusion helper · level 1 · ran ·
314f5264c2883265 - LDVAE helper · level 1 · ran ·
933b8e67ac23c0ad - MultiheadAttention model · level 0 · unverified ·
b3b023b4c6805594 - NLLSurvLoss helper · level 1 · ran ·
b8a656d552c1f7f0 - SNN_Block helper · level 1 · ran · our draft was wrong ·
10482673211edd0c - VIBTrans helper · level 0 · unverified ·
c41f70496ff795c3 - calc_W_loss helper · level 1 · ran · our draft was wrong ·
98bab5b56a287e4d - calc_kl_divergence helper · level 1 · ran · our draft was wrong ·
d9f70b6ed26bc6dc - reparameterize helper · level 1 · ran · our draft was wrong ·
3cd91116c815d020 - Decoder_Share helper · level 1 · ran ·
44e3a3d761a3d791 - Decoder_Specific helper · level 1 · ran ·
796cffef10d94448 - Encoder_TRANSFORMER helper · level 1 · ran ·
5cf9ee8e784759c2 - prior_expert helper · level 1 · ran · our draft was wrong ·
28023ddd28326523 - multi_head_attention_forward model · level 0 · unverified ·
4043b3b3f31ca073 - nll_loss helper · level 1 · ran; the contract check could not run (RAISES) ·
62ede8fe77ab4913 - PPEG helper · level 1 · ran ·
7cc8eaf772224044 - TransLayer helper · level 0 · unverified ·
22eac946d1b47bb1 - NystromAttention helper · level 1 · ran ·
d4e04018342ece86 - exists helper · level 1 · ran · violated contract ·
aa5486a3650902d8 - moore_penrose_iter_pinv helper · level 0 · unverified ·
763d48b1144254cd
harvested Assembly for Multimodal Optimal Transport-based Co-Attention Transformer (graph method: Multimodal Optimal Transport-based Co-Attention Transformer). 2 bricks; individually on a fixture: 0 ran · 2 unverified. The assembly has not been run end-to-end.
one of 3 siblings
- MOTCAT_Surv entry · level 0 · unverified ·
82db0b1414d840c6 - OT_Attn_assem model · level 0 · unverified ·
eee6a34fb548d0d6
Each brick ends with its code_sha256, Syntology's identity for that exact code; click one to copy the get_code call that returns it. For agents, on Syntology's MCP service: assembly(arxiv_id="2306.08330") returns these assemblies with each brick's role and wiring (how to connect).
Tasks
Results from the paper archive 2025-07-28
No leaderboard rows for this paper in the archive.
Methods
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