Papers › PASSION: Towards Effective Incomplete Multi-Modal Medical Image Segmentation with...

PASSION: Towards Effective Incomplete Multi-Modal Medical Image Segmentation with Imbalanced Missing Rates

20 Jul 2024arXiv:2407.14796archive 2025-07-28

Junjie Shi, Caozhi Shang, Zhaobin Sun, Li Yu, Xin Yang, Zengqiang Yan

Incomplete multi-modal image segmentation is a fundamental task in medical imaging to refine deployment efficiency when only partial modalities are available. However, the common practice that complete-modality data is visible during model training is far from realistic, as modalities can have imbalanced missing rates in clinical scenarios. In this paper, we, for the first time, formulate such a challenging setting and propose Preference-Aware Self-diStillatION (PASSION) for incomplete multi-modal medical image segmentation under imbalanced missing rates. Specifically, we first construct pixel-wise and semantic-wise self-distillation to balance the optimization objective of each modality. Then, we define relative preference to evaluate the dominance of each modality during training, based on which to design task-wise and gradient-wise regularization to balance the convergence rates of different modalities. Experimental results on two publicly available multi-modal datasets demonstrate the superiority of PASSION against existing approaches for modality balancing. More importantly, PASSION is validated to work as a plug-and-play module for consistent performance improvement across different backbones. Code is available at https://github.com/Jun-Jie-Shi/PASSION.

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 16 code samples harvested from 1 repository linked to this paper: 15 ran (of which 0 constructed an object rather than computing a result; 9 with no instrument failure: 1 honoured, 1 violated, 7 with no contract checked; 6 where Syntology's instrument failed) · 1 unverified. Where Syntology's instrument failed: 4 where our contract draft was wrong; 2 where the contract check could not run; failures of Syntology's instrument, not of the code.

By repository: official repository: 16 samples from 1 repository, 15 ran (9 with no instrument failure; 6 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.

jun-jie-shi/passion officialmentioned in papermentioned on GitHubpytorchApache-2.0Syntology: 16 samples, 15 ran (6 instrument-failed) · 1 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

16 samples harvested: 15 ran (of which 0 constructed an object rather than computing a result; 9 with no instrument failure: 1 honoured, 1 violated, 7 with no contract checked; 6 where Syntology's instrument failed) · 1 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
1ran · violated contract
4ran · our draft was wrong
2ran; the contract check could not run
7ran
1unverified

Licence: 0 of the 16 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 jun-jie-shi/passion. “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.

jun-jie-shi/passion official repository 16 samples, 15 ran (6 instrument-failed) · 1 unverified
Js_div code/utils/lr_scheduler.py ran Apache-2.0 (permissive) · 4c2097366a0c9a24 · report fixture: signature p:Tensor/2/float, q:Tensor/2/float, KLDivLoss:callable/0/? · returned Tensor · level recorded 2026-09-24
crop in 99 papers
census: 5 implementations from 5 papers, 4 distinct outputs across 4 buckets, one shared input per bucket
code/preprocessing/preprocess_brats.py ran; the contract check could not run (RAISES) Apache-2.0 (permissive) · fb26dcccfaf8fbc6 · report fixture: signature vol:ndarray/3/float · returned tuple · level recorded 2026-09-24
dice_loss in 193 papers
census: 10 implementations from 16 papers, 7 distinct outputs across 4 buckets, one shared input per bucket
code/utils/criterions.py ran Apache-2.0 (permissive) · 672eefec7e9131bc · report fixture: signature output:Tensor/5/float, target:Tensor/5/int, num_cls:int/0/int, eps:float/0/float, up_op:callable/0/? · returned Tensor · level recorded 2026-09-24
dice_loss_bs code/utils/criterions.py ran Apache-2.0 (permissive) · 873433db15bc1e4d · report fixture: signature output:Tensor/5/float, target:Tensor/5/float, num_cls:int/0/int, eps:float/0/float, up_op:callable/0/? · returned Tensor · level recorded 2026-09-24
get_params in 53 papers code/utils/lr_scheduler.py ran · our draft was wrong Apache-2.0 (permissive) · d51dae9ac1ba0359 · report fixture: signature model:callable/0/? · returned tuple · level recorded 2026-09-24
get_temperature code/utils/lr_scheduler.py ran · honoured contract fingerprinted Apache-2.0 (permissive) · 2675ee5f110411e2 · report fixture: signature epoch:int/0/int · returned int · level recorded 2026-09-24
mask_gen_cross4 code/models/mask.py ran Apache-2.0 (permissive) · 7f3257ab27f6ac4d · report fixture: signature Batchsize:int/0/int, K:int/0/int, C:int/0/int, mask:Tensor/2/int · returned Tensor · level recorded 2026-09-24
mask_gen_fusion code/models/mask.py ran Apache-2.0 (permissive) · 35e8e3aef9fcc772 · report fixture: signature Batchsize:int/0/int, NumHead:int/0/int, patches:int/0/int, NumClass:int/0/int, mask:Tensor/2/int · returned Tensor · level recorded 2026-09-24
nchwd2nlc2nchwd code/models/blocks.py ran; the contract check could not run (RAISES) Apache-2.0 (permissive) · c7dfb8d3e7844879 · report fixture: signature module:callable/0/?, x:Tensor/5/float · returned Tensor · level recorded 2026-09-24
normalization in 70 papers
census: 4 implementations from 6 papers, 4 distinct outputs across 3 buckets, one shared input per bucket
code/models/blocks.py ran · our draft was wrong Apache-2.0 (permissive) · 268e21ea88a8ccb1 · report fixture: signature planes:int/0/int, norm:str/0/str · returned BatchNorm3d · level recorded 2026-09-24
normalize in 638 papers
census: 70 implementations from 82 papers, 51 distinct outputs across 11 buckets, one shared input per bucket
code/preprocessing/preprocess_brats.py ran · violated contract Apache-2.0 (permissive) · 8ee9fb4494c15e91 · report fixture: signature vol:Tensor/4/float · returned Tensor · level recorded 2026-09-24
parse in 85 papers code/utils/parser.py ran · our draft was wrong Apache-2.0 (permissive) · 8a289ba730141ed4 · report fixture: signature d:dict/0/? · returned AttrDict · level recorded 2026-09-24
softmax_weighted_loss code/utils/criterions.py ran Apache-2.0 (permissive) · b5ee99865309afa1 · report fixture: signature output:Tensor/5/float, target:Tensor/5/float, num_cls:int/0/int, up_op:callable/0/? · returned Tensor · level recorded 2026-09-24
split_data in 68 papers code/preprocessing/data_split.py ran · our draft was wrong Apache-2.0 (permissive) · 4663b0d3de392cbf · report fixture: signature image_path:str/0/str · returned tuple · level recorded 2026-09-24
sup_128 code/preprocessing/preprocess_brats.py ran fingerprinted Apache-2.0 (permissive) · 3153dadb37e140a0 · report fixture: signature xmin:int/0/int, xmax:int/0/int · returned tuple · level recorded 2026-09-24
load in 392 papers code/utils/parser.py unverified Apache-2.0 (permissive) · b40f27cd88000a35 · report

Tasks

Image SegmentationMedical Image SegmentationMulti-modal image segmentationSemantic Segmentation

Results from the paper archive 2025-07-28

No leaderboard rows for this paper in the archive.

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