Papers › Deep Unfolding Convolutional Dictionary Model for Multi-Contrast MRI Super-resolution...

Deep Unfolding Convolutional Dictionary Model for Multi-Contrast MRI Super-resolution and Reconstruction

3 Sep 2023arXiv:2309.01171archive 2025-07-28

Pengcheng Lei, Faming Fang, Guixu Zhang, Ming Xu

Magnetic resonance imaging (MRI) tasks often involve multiple contrasts. Recently, numerous deep learning-based multi-contrast MRI super-resolution (SR) and reconstruction methods have been proposed to explore the complementary information from the multi-contrast images. However, these methods either construct parameter-sharing networks or manually design fusion rules, failing to accurately model the correlations between multi-contrast images and lacking certain interpretations. In this paper, we propose a multi-contrast convolutional dictionary (MC-CDic) model under the guidance of the optimization algorithm with a well-designed data fidelity term. Specifically, we bulid an observation model for the multi-contrast MR images to explicitly model the multi-contrast images as common features and unique features. In this way, only the useful information in the reference image can be transferred to the target image, while the inconsistent information will be ignored. We employ the proximal gradient algorithm to optimize the model and unroll the iterative steps into a deep CDic model. Especially, the proximal operators are replaced by learnable ResNet. In addition, multi-scale dictionaries are introduced to further improve the model performance. We test our MC-CDic model on multi-contrast MRI SR and reconstruction tasks. Experimental results demonstrate the superior performance of the proposed MC-CDic model against existing SOTA methods. Code is available at https://github.com/lpcccc-cv/MC-CDic.

PaperPDFCodeCode Syntology ranMethod as code

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

By repository: official repository: 14 samples from 1 repository, 11 ran (10 with no instrument failure; 1 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-25 (UTC): the dates Syntology's graph wrote each sample's verification level, not when the code executed.

lpcccc-cv/mc-cdic officialmentioned in paperpytorchSyntology: 14 samples, 11 ran (1 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

14 samples harvested: 11 ran (of which 9 constructed an object rather than computing a result; 10 with no instrument failure: 0 honoured, 0 violated, 10 with no contract checked; 1 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 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.

1ran · our draft was wrong
10ran
3unverified

Licence: 0 of the 14 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 lpcccc-cv/mc-cdic. “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 5 samples 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. 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.

lpcccc-cv/mc-cdic official repository 14 samples, 11 ran (1 instrument-failed) · 3 unverified
RCAB in 6 papers models/modules/MCCDic.py ran · metamorphic tier: deterministic fingerprinted MIT (permissive) · c932a7c227b3fbd2 · report fixture: returned RCAB · level recorded 2026-09-22
ResidualGroup in 10 papers models/modules/MCCDic.py ran · metamorphic tier: deterministic MIT (permissive) · 4b600ebf1fc6ebb7 · report fixture: returned ResidualGroup · level recorded 2026-09-22
adjoint_conv_op models/modules/MCCDic.py ran · metamorphic tier: deterministic fingerprinted MIT (permissive) · a638d774495f33d0 · report fixture: returned adjoint_conv_op · level recorded 2026-09-22
adjoint_out_conv models/modules/MCCDic.py ran · metamorphic tier: deterministic fingerprinted MIT (permissive) · 73e7cb76f7d24163 · report fixture: returned adjoint_out_conv · level recorded 2026-09-22
adjoint_up_block models/modules/MCCDic.py ran · metamorphic tier: deterministic MIT (permissive) · 34942e88e75a2bcc · report fixture: returned adjoint_up_block · level recorded 2026-09-22
decoder in 19 papers models/modules/MCCDic.py ran · metamorphic tier: deterministic MIT (permissive) · d3f68ff5225090da · report fixture: returned decoder · level recorded 2026-09-22
dictionary_model models/modules/MCCDic.py ran · metamorphic tier: deterministic MIT (permissive) · 91f3898d354e32df · report fixture: returned dictionary_model · level recorded 2026-09-22
get_all_conv models/modules/MCCDic.py ran · our draft was wrong MIT (permissive) · 10477cfab194e8de · report fixture: signature net:callable/0/?, conv_list:list/1/empty · returned list · level recorded 2026-09-22
out_conv models/modules/MCCDic.py ran · metamorphic tier: deterministic fingerprinted MIT (permissive) · 523343cc02eabea1 · report fixture: returned out_conv · level recorded 2026-09-22
relu in 58 papers
census: 8 implementations from 11 papers, 4 distinct outputs across 2 buckets, one shared input per bucket
models/modules/MCCDic.py ran fingerprinted MIT (permissive) · e87a5885334f0de1 · report fixture: signature x:Tensor/2/float, lambd:Tensor/2/float · returned Tensor · level recorded 2026-09-25
up_block in 6 papers models/modules/MCCDic.py ran · metamorphic tier: deterministic MIT (permissive) · a0158adc8e09beea · report fixture: returned up_block · level recorded 2026-09-22
MCCDic models/modules/MCCDic.py unverified MIT (permissive) · 891178fb9c64214c · report
adjoint_dictionary_model models/modules/MCCDic.py unverified MIT (permissive) · 4e0ef546f602c8fa · report
ista_unet models/modules/MCCDic.py unverified MIT (permissive) · d8c61bda1dfa9cf4 · 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.

1 assembly on this paper: 1 harvested, 0 generated.

harvested Assembly for MC-CDic (graph method: MC-CDic). 15 bricks; individually on a fixture: 12 ran (of which 10 constructed an object rather than computing a result; 11 with no instrument failure: 0 honoured, 0 violated, 11 with no contract checked; 1 where Syntology's instrument failed) · 3 unverified. The assembly has not been run end-to-end.

  1. MCCDic entry · level 0 · unverified · 891178fb9c64214c
  2. decoder helper · level 1 · ran · d3f68ff5225090da
  3. ista_unet model · level 0 · unverified · d8c61bda1dfa9cf4
  4. ResidualGroup model · level 1 · ran · 4b600ebf1fc6ebb7
  5. adjoint_dictionary_model helper · level 0 · unverified · 4e0ef546f602c8fa
  6. dictionary_model model · level 1 · ran · 91f3898d354e32df
  7. get_all_conv helper · level 1 · ran · our draft was wrong · 10477cfab194e8de
  8. relu helper · level 1 · ran · e87a5885334f0de1
  9. RCAB model · level 1 · ran · c932a7c227b3fbd2
  10. adjoint_conv_op helper · level 1 · ran · a638d774495f33d0
  11. adjoint_out_conv model · level 1 · ran · 73e7cb76f7d24163
  12. adjoint_up_block model · level 1 · ran · 34942e88e75a2bcc
  13. out_conv model · level 1 · ran · 523343cc02eabea1
  14. up_block model · level 1 · ran · a0158adc8e09beea
  15. CALayer model · level 1 · ran · 0802c53335f5c2fc

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="2309.01171") returns these assemblies with each brick's role and wiring (how to connect).

Tasks

Super-Resolution

Results from the paper archive 2025-07-28

No leaderboard rows for this paper in the archive.

Methods

1x1 ConvolutionAverage PoolingBatch NormalizationBottleneck Residual BlockConvolutionGlobal Average PoolingKaiming InitializationMax PoolingReLUResidual BlockResidual Connection

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