Papers › CMUNeXt: An Efficient Medical Image Segmentation Network based on Large Kernel and Skip Fusion

CMUNeXt: An Efficient Medical Image Segmentation Network based on Large Kernel and Skip Fusion

2 Aug 2023arXiv:2308.01239archive 2025-07-28

Fenghe Tang, Jianrui Ding, Lingtao Wang, Chunping Ning, S. Kevin Zhou

The U-shaped architecture has emerged as a crucial paradigm in the design of medical image segmentation networks. However, due to the inherent local limitations of convolution, a fully convolutional segmentation network with U-shaped architecture struggles to effectively extract global context information, which is vital for the precise localization of lesions. While hybrid architectures combining CNNs and Transformers can address these issues, their application in real medical scenarios is limited due to the computational resource constraints imposed by the environment and edge devices. In addition, the convolutional inductive bias in lightweight networks adeptly fits the scarce medical data, which is lacking in the Transformer based network. In order to extract global context information while taking advantage of the inductive bias, we propose CMUNeXt, an efficient fully convolutional lightweight medical image segmentation network, which enables fast and accurate auxiliary diagnosis in real scene scenarios. CMUNeXt leverages large kernel and inverted bottleneck design to thoroughly mix distant spatial and location information, efficiently extracting global context information. We also introduce the Skip-Fusion block, designed to enable smooth skip-connections and ensure ample feature fusion. Experimental results on multiple medical image datasets demonstrate that CMUNeXt outperforms existing heavyweight and lightweight medical image segmentation networks in terms of segmentation performance, while offering a faster inference speed, lighter weights, and a reduced computational cost. The code is available at https://github.com/FengheTan9/CMUNeXt.

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 6 code samples harvested from 2 repositories linked to this paper: 6 ran (of which 0 constructed an object rather than computing a result; 0 with no instrument failure: 0 honoured, 0 violated, 0 with no contract checked; 6 where Syntology's instrument failed) · 0 unverified. Where Syntology's instrument failed: 6 where the contract check could not run; failures of Syntology's instrument, not of the code. Every run on this page is a failure of Syntology's instrument, not of the code.

By repository: official repository: 6 samples from 2 repositories, 6 ran (0 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-22 (UTC): the dates Syntology's graph wrote each sample's verification level, not when the code executed.

fenghetan9/cmunext officialmentioned in papermentioned on GitHubpytorchSyntology: 3 samples, 3 ran (3 instrument-failed) · 0 unverified report
FengheTan9/Medical-Image-Segmentation-Benchmarks officialmentioned on GitHubpytorchSyntology: 3 samples, 3 ran (3 instrument-failed) · 0 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

6 samples harvested: 6 ran (of which 0 constructed an object rather than computing a result; 0 with no instrument failure: 0 honoured, 0 violated, 0 with no contract checked; 6 where Syntology's instrument failed) · 0 unverified. “Where Syntology's instrument failed” counts failures of Syntology's instrument, not of the code. Every run on this page is a failure 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.

6ran; the contract check could not run

Licence: 0 of the 6 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 2 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”. “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.

fenghetan9/cmunext official repository 3 samples, 3 ran (3 instrument-failed) · 0 unverified
cmunext network/CMUNeXt.py ran; the contract check could not run (RAISES) · metamorphic tier: deterministic MIT (permissive) · bf04d5cb1c5ac265 · report fixture: signature dims:list/1/int, depths:list/1/int, kernels:list/1/int · returned CMUNeXt · level recorded 2026-09-22
cmunext_l network/CMUNeXt.py ran; the contract check could not run (RAISES) · metamorphic tier: deterministic MIT (permissive) · 3eb64626017a438d · report fixture: signature dims:list/1/int, depths:list/1/int, kernels:list/1/int · returned CMUNeXt · level recorded 2026-09-22
cmunext_s network/CMUNeXt.py ran; the contract check could not run (RAISES) · metamorphic tier: deterministic MIT (permissive) · 49a9d4657a5e4202 · report fixture: signature dims:list/1/int, depths:list/1/int, kernels:list/1/int · returned CMUNeXt · level recorded 2026-09-22
FengheTan9/Medical-Image-Segmentation-Benchmarks official repository 3 samples, 3 ran (3 instrument-failed) · 0 unverified
cmunext src/network/conv_based/CMUNeXt.py ran; the contract check could not run (RAISES) · metamorphic tier: deterministic MIT (permissive) · bb0ec52db8c08f8b · report fixture: signature input_channel:int/0/int, num_classes:int/0/int, dims:list/1/int, depths:list/1/int, kernels:list/1/int · returned CMUNeXt · level recorded 2026-09-22
cmunext_l src/network/conv_based/CMUNeXt.py ran; the contract check could not run (RAISES) · metamorphic tier: deterministic MIT (permissive) · d3357bba5ec10caa · report fixture: signature input_channel:int/0/int, num_classes:int/0/int, dims:list/1/int, depths:list/1/int, kernels:list/1/int · returned CMUNeXt · level recorded 2026-09-22
cmunext_s src/network/conv_based/CMUNeXt.py ran; the contract check could not run (RAISES) · metamorphic tier: deterministic MIT (permissive) · 7a2fe13df6fab09e · report fixture: signature input_channel:int/0/int, num_classes:int/0/int, dims:list/1/int, depths:list/1/int, kernels:list/1/int · returned CMUNeXt · level recorded 2026-09-22

Tasks

Image SegmentationInductive BiasMedical Image SegmentationSegmentationSemantic Segmentation

Results from the paper archive 2025-07-28

No leaderboard rows for this paper in the archive.

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