Papers › HUMUS-Net: Hybrid unrolled multi-scale network architecture for accelerated MRI reconstruction

HUMUS-Net: Hybrid unrolled multi-scale network architecture for accelerated MRI reconstruction

15 Mar 2022arXiv:2203.08213archive 2025-07-28

Zalan Fabian, Berk Tınaz, Mahdi Soltanolkotabi

In accelerated MRI reconstruction, the anatomy of a patient is recovered from a set of under-sampled and noisy measurements. Deep learning approaches have been proven to be successful in solving this ill-posed inverse problem and are capable of producing very high quality reconstructions. However, current architectures heavily rely on convolutions, that are content-independent and have difficulties modeling long-range dependencies in images. Recently, Transformers, the workhorse of contemporary natural language processing, have emerged as powerful building blocks for a multitude of vision tasks. These models split input images into non-overlapping patches, embed the patches into lower-dimensional tokens and utilize a self-attention mechanism that does not suffer from the aforementioned weaknesses of convolutional architectures. However, Transformers incur extremely high compute and memory cost when 1) the input image resolution is high and 2) when the image needs to be split into a large number of patches to preserve fine detail information, both of which are typical in low-level vision problems such as MRI reconstruction, having a compounding effect. To tackle these challenges, we propose HUMUS-Net, a hybrid architecture that combines the beneficial implicit bias and efficiency of convolutions with the power of Transformer blocks in an unrolled and multi-scale network. HUMUS-Net extracts high-resolution features via convolutional blocks and refines low-resolution features via a novel Transformer-based multi-scale feature extractor. Features from both levels are then synthesized into a high-resolution output reconstruction. Our network establishes new state of the art on the largest publicly available MRI dataset, the fastMRI dataset. We further demonstrate the performance of HUMUS-Net on two other popular MRI datasets and perform fine-grained ablation studies to validate our design.

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 5 code samples harvested from 1 repository linked to this paper: 5 ran (of which 0 constructed an object rather than computing a result; 2 with no instrument failure: 0 honoured, 0 violated, 2 with no contract checked; 3 where Syntology's instrument failed) · 0 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: 5 samples from 1 repository, 5 ran (2 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.

MathFLDS/HUMUS-Net officialmentioned in papermentioned on GitHubpytorchMITSyntology: 5 samples, 5 ran (3 instrument-failed) · 0 unverified report
z-fabian/HUMUS-Net officialmentioned on GitHubpytorchMITSyntology: not harvested 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

5 samples harvested: 5 ran (of which 0 constructed an object rather than computing a result; 2 with no instrument failure: 0 honoured, 0 violated, 2 with no contract checked; 3 where Syntology's instrument failed) · 0 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.

2ran · our draft was wrong
1ran; the contract check could not run
2ran

Licence: 3 of the 5 samples are pointer only, meaning Syntology does not serve that copy's text. For 3 of them, this paper's copy is under a permissive licence and cleared, but the stored copy of the same code that Syntology serves is not; the licence label's tooltip gives Syntology's recorded reason. This page shows no code text for any sample; each one links to its file in the repository.

Harvested from MathFLDS/HUMUS-Net. “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.

MathFLDS/HUMUS-Net official repository 5 samples, 5 ran (3 instrument-failed) · 0 unverified
batched_mask_center models/humus_net.py ran MIT (permissive) here; the stored copy is pointer only · f8ec18034e33feb4 · report fixture: signature x:Tensor/4/float, mask_from:Tensor/1/int, mask_to:Tensor/1/int · returned Tensor · level recorded 2026-09-24
load_args_from_config humus_examples/utils.py ran · our draft was wrong MIT (permissive) here; the stored copy is pointer only · 1b315f2b67a89eab · report fixture: signature args:Args/0/? · returned Args · level recorded 2026-09-24
mask_center models/humus_net.py ran fingerprinted MIT (permissive) here; the stored copy is pointer only · bdf81e063710a085 · report fixture: signature x:Tensor/4/float, mask_from:int/0/int, mask_to:int/0/int · returned Tensor · level recorded 2026-09-24
window_partition in 377 papers
census: 13 implementations from 17 papers, 5 distinct outputs across 3 buckets, one shared input per bucket
models/humus_block.py ran; the contract check could not run (RAISES) · metamorphic tier: invariant fingerprinted MIT (permissive) · f9fd6241d935f07b · report fixture: signature x:Tensor/4/float, window_size:int/0/int · returned Tensor · level recorded 2026-09-22
window_reverse in 296 papers models/humus_block.py ran · our draft was wrong MIT (permissive) · fb32094c6dbece71 · report fixture: signature windows:Tensor/4/float, window_size:int/0/int, H:int/0/int, W:int/0/int · returned Tensor · level recorded 2026-09-22

Tasks

AnatomyMRI Reconstruction

Results from the paper archive 2025-07-28

TaskDatasetModelMetricValueRank at snapshotLeaderboardReport
MRI Reconstruction fastMRI Knee 8x HUMUS-Net (train+val data) PSNR 37.3 #1 of 4 Archive leaderboard report
MRI Reconstruction fastMRI Knee 8x HUMUS-Net (train+val data) SSIM 0.8945 #1 of 4 Archive leaderboard report
MRI Reconstruction fastMRI Knee 8x HUMUS-Net (train only) PSNR 37.0 #2 of 4 Archive leaderboard report
MRI Reconstruction fastMRI Knee 8x HUMUS-Net (train only) SSIM 0.8936 #2 of 4 Archive leaderboard report
MRI Reconstruction fastMRI Knee Val 8x HUMUS-Net-L NMSE 0.0086 #2 of 4 Archive leaderboard report
MRI Reconstruction fastMRI Knee Val 8x HUMUS-Net-L PSNR 37.45 #2 of 4 Archive leaderboard report
MRI Reconstruction fastMRI Knee Val 8x HUMUS-Net-L Params (M) 228 #2 of 4 Archive leaderboard report
MRI Reconstruction fastMRI Knee Val 8x HUMUS-Net-L SSIM 0.8955 #2 of 4 Archive leaderboard report
MRI Reconstruction fastMRI Knee Val 8x HUMUS-Net NMSE 0.0090 #3 of 4 Archive leaderboard report
MRI Reconstruction fastMRI Knee Val 8x HUMUS-Net PSNR 37.20 #3 of 4 Archive leaderboard report
MRI Reconstruction fastMRI Knee Val 8x HUMUS-Net Params (M) 109 #3 of 4 Archive leaderboard report
MRI Reconstruction fastMRI Knee Val 8x HUMUS-Net SSIM 0.8946 #3 of 4 Archive leaderboard report

Ranks are positions in the archive's leaderboards as they stood at the 2025-07-28 snapshot. Results published since then are not among these rows, so a rank here is not a current standing.

Methods

Absolute Position EncodingsAdamAttentionBPEDense ConnectionsDropoutLabel SmoothingLayer NormalizationLinear LayerMulti-Head AttentionPosition-Wise Feed-Forward LayerResidual ConnectionSoftmaxTransformer

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