Papers › ControlFusion: A Controllable Image Fusion Framework with Language-Vision Degradation Prompts

ControlFusion: A Controllable Image Fusion Framework with Language-Vision Degradation Prompts

30 Mar 2025arXiv:2503.23356archive 2025-07-28

Linfeng Tang, Yeda Wang, Zhanchuan Cai, Junjun Jiang, Jiayi Ma

Current image fusion methods struggle to address the composite degradations encountered in real-world imaging scenarios and lack the flexibility to accommodate user-specific requirements. In response to these challenges, we propose a controllable image fusion framework with language-vision prompts, termed ControlFusion, which adaptively neutralizes composite degradations. On the one hand, we develop a degraded imaging model that integrates physical imaging mechanisms, including the Retinex theory and atmospheric scattering principle, to simulate composite degradations, thereby providing potential for addressing real-world complex degradations from the data level. On the other hand, we devise a prompt-modulated restoration and fusion network that dynamically enhances features with degradation prompts, enabling our method to accommodate composite degradation of varying levels. Specifically, considering individual variations in quality perception of users, we incorporate a text encoder to embed user-specified degradation types and severity levels as degradation prompts. We also design a spatial-frequency collaborative visual adapter that autonomously perceives degradations in source images, thus eliminating the complete dependence on user instructions. Extensive experiments demonstrate that ControlFusion outperforms SOTA fusion methods in fusion quality and degradation handling, particularly in countering real-world and compound degradations with various levels.

PaperPDFCode 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 5 code samples harvested from 1 repository linked to this paper: 4 ran (of which 4 constructed an object rather than computing a result; 4 with no instrument failure: 0 honoured, 0 violated, 4 with no contract checked; 0 where Syntology's instrument failed) · 1 unverified; every one of the 4 samples that ran constructed an object rather than computing a result. “Where Syntology's instrument failed” counts failures of Syntology's instrument, not of the code; here there are none.

By repository: found in paper text by Syntology: 5 samples from 1 repository, 4 ran (4 with no instrument failure; 0 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.

Linfeng-Tang/ControlFusion found in paper text by SyntologySyntology: 5 samples, 4 ran (0 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

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

4ran
1unverified

Licence: 5 of the 5 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 Linfeng-Tang/ControlFusion. “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 2 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.

Linfeng-Tang/ControlFusion found in paper text by Syntology 5 samples, 4 ran (0 instrument-failed) · 1 unverified
CBAM in 6 papers model/ControlFusion.py ran no licence file found · pointer only · 81c9126ff30f676e · report fixture: returned CBAM · level recorded 2026-09-22
ChannelAttention in 14 papers model/ControlFusion.py ran no licence file found · pointer only · 6a8e0a2cdf7f3144 · report fixture: returned ChannelAttention · level recorded 2026-09-22
FeatureWiseAffine model/ControlFusion.py ran fingerprinted no licence file found · pointer only · f8dfe4829be56442 · report fixture: returned FeatureWiseAffine · level recorded 2026-09-22
SpatialAttention in 17 papers model/ControlFusion.py ran fingerprinted no licence file found · pointer only · 4a9889e4b1b18fc3 · report fixture: returned SpatialAttention · level recorded 2026-09-22
ControlFusion model/ControlFusion.py unverified no licence file found · pointer only · 8c5aad72ddb1c773 · 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 ControlFusion (graph method: ControlFusion). 21 bricks; individually on a fixture: 18 ran (of which 15 constructed an object rather than computing a result; 16 with no instrument failure: 0 honoured, 0 violated, 16 with no contract checked; 2 where Syntology's instrument failed) · 3 unverified. The assembly has not been run end-to-end.

  1. ControlFusion entry · level 0 · unverified · 8c5aad72ddb1c773
  2. Attention_spatial model · level 1 · ran · 83202c7c9a0463f9
  3. CBAM model · level 1 · ran · 81c9126ff30f676e
  4. Cross_attention model · level 1 · ran · cddd2a7c1f722c27
  5. Encoder_A model · level 0 · unverified · 4b0d0703eb4d78e0
  6. Encoder_B model · level 0 · unverified · b88e105766635778
  7. FeatureWiseAffine model · level 1 · ran · f8dfe4829be56442
  8. Fusion_Embed model · level 1 · ran · adea59d97c2173b5
  9. TransformerBlock model · level 1 · ran · 3bec9331e88709b1
  10. Upsample helper · level 1 · ran · a334b6b5228fd884
  11. ChannelAttention model · level 1 · ran · 6a8e0a2cdf7f3144
  12. SpatialAttention model · level 1 · ran · 4a9889e4b1b18fc3
  13. Downsample helper · level 1 · ran · 43cd6fa3751bab78
  14. OverlapPatchEmbed helper · level 1 · ran · 099f2dc5f59fa05f
  15. Attention helper · level 1 · ran · 98e962e3944f0fb6
  16. FeedForward helper · level 1 · ran · b88cfeea8c3a8562
  17. LayerNorm helper · level 1 · ran · 7add138148389ff5
  18. BiasFree_LayerNorm helper · level 1 · ran · db9f0e70f3f18049
  19. WithBias_LayerNorm helper · level 1 · ran · 1d90d30671b0d4b8
  20. to_3d helper · level 1 · ran; the contract check could not run · 82a15cc1e46f7e4d
  21. to_4d helper · level 1 · ran; the contract check could not run · b20f2a5df739a59e

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

Results from the paper archive 2025-07-28

No leaderboard rows for this paper in the archive.

Methods

Adapter

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