Papers › Towards Highly Realistic Artistic Style Transfer via Stable Diffusion with Step-aware...
Towards Highly Realistic Artistic Style Transfer via Stable Diffusion with Step-aware and Layer-aware Prompt
Zhanjie Zhang, Quanwei Zhang, Huaizhong Lin, Wei Xing, Juncheng Mo, Shuaicheng Huang, Jinheng Xie, Guangyuan Li, Junsheng Luan, Lei Zhao, Dalong Zhang, Lixia Chen
Artistic style transfer aims to transfer the learned artistic style onto an arbitrary content image, generating artistic stylized images. Existing generative adversarial network-based methods fail to generate highly realistic stylized images and always introduce obvious artifacts and disharmonious patterns. Recently, large-scale pre-trained diffusion models opened up a new way for generating highly realistic artistic stylized images. However, diffusion model-based methods generally fail to preserve the content structure of input content images well, introducing some undesired content structure and style patterns. To address the above problems, we propose a novel pre-trained diffusion-based artistic style transfer method, called LSAST, which can generate highly realistic artistic stylized images while preserving the content structure of input content images well, without bringing obvious artifacts and disharmonious style patterns. Specifically, we introduce a Step-aware and Layer-aware Prompt Space, a set of learnable prompts, which can learn the style information from the collection of artworks and dynamically adjusts the input images' content structure and style pattern. To train our prompt space, we propose a novel inversion method, called Step-ware and Layer-aware Prompt Inversion, which allows the prompt space to learn the style information of the artworks collection. In addition, we inject a pre-trained conditional branch of ControlNet into our LSAST, which further improved our framework's ability to maintain content structure. Extensive experiments demonstrate that our proposed method can generate more highly realistic artistic stylized images than the state-of-the-art artistic style transfer methods.
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):
get_harvested_code_for_paper(arxiv_id="2404.11474")get_code(code_sha256="…")with a sample'scode_sha256from the list belowget_citation_path(paper_1="2404.11474", paper_2="…")with another paper's arXiv id or titleget_concepts_for_paper(arxiv_id="2404.11474")
Code
Syntology 20 code samples harvested from 1 repository linked to this paper: 10 ran (of which 3 constructed an object rather than computing a result; 3 with no instrument failure: 0 honoured, 0 violated, 3 with no contract checked; 7 where Syntology's instrument failed) · 10 unverified. Where Syntology's instrument failed: 7 where our contract draft was wrong; failures of Syntology's instrument, not of the code.
By repository: official repository: 20 samples from 1 repository, 10 ran (3 with no instrument failure; 7 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. 1 of the 10 samples that ran has no recorded date.
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
20 samples harvested: 10 ran (of which 3 constructed an object rather than computing a result; 3 with no instrument failure: 0 honoured, 0 violated, 3 with no contract checked; 7 where Syntology's instrument failed) · 10 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.
Licence: 4 of the 20 samples are pointer only, meaning Syntology does not serve that copy's text. For 4 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 jamie-cheung/lsast. “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.
69360f5b0cc8f069 · report
fixture: returned CheckpointFunction · level recorded 2026-09-22 edd0dbdde64951f7 · report
fixture: returned CrossAttention · level recorded 2026-09-22 713884729e861c62 · report
fixture: returned MemoryEfficientCrossAttention · level recorded 2026-09-22 c3a6b977022957cb · report
fixture: signature in_channels:int/0/int · returned GroupNorm · level recorded, date not recorded census: 5 implementations from 7 papers, 2 distinct outputs on one shared input cldm/cldm.py ran · our draft was wrong fingerprinted Apache-2.0 (permissive) ·
a0ab4de8a03b69b0 · report
fixture: signature content_feat:Tensor/4/float, style_feat:Tensor/4/float · returned Tensor · level recorded 2026-09-24 98f385d847636a3e · report
fixture: signature text:str/0/str · returned str · level recorded 2026-09-22 6576c5264bea5331 · report
fixture: signature feat:Tensor/4/float, eps:float/0/float · returned tuple · level recorded 2026-09-24 d919ae32e5e4e616 · report
fixture: signature word:tuple/1/str · returned set · level recorded 2026-09-22 cfc17707f35e7ec4 · report
fixture: signature d:dict/0/? · returned dict · level recorded 2026-09-25 9542161e9640b858 · report
fixture: signature text:str/0/str · returned str · level recorded 2026-09-22 b6dff222c0e9edfe · report
cd763b5f891b0938 · report
census: 6 implementations from 5 papers, 6 distinct outputs across 2 buckets, one shared input per bucket cldm/cldm.py unverified Apache-2.0 (permissive) ·
66e12c88bac640da · report
406611ffc8d44703 · report
1c67e34b46237f50 · report
39e6b23b55f376ea · report
f6f30e41636ae569 · report
df733a879693145d · 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 LSAST (graph method: LSAST). 29 bricks; individually on a fixture: 18 ran (of which 10 constructed an object rather than computing a result; 12 with no instrument failure: 0 honoured, 2 violated, 10 with no contract checked; 6 where Syntology's instrument failed) · 11 unverified. The assembly has not been run end-to-end.
- ControlNet_style entry · level 0 · unverified ·
60d938a3fe7521c0 - AttentionBlock helper · level 0 · unverified ·
b6dff222c0e9edfe - Downsample helper · level 1 · ran ·
0feab49c606075bb - ResBlock helper · level 0 · unverified ·
66e12c88bac640da - SpatialTransformer helper · level 0 · unverified ·
406611ffc8d44703 - TimestepEmbedSequential helper · level 0 · unverified ·
1c67e34b46237f50 - conv_nd helper · level 0 · unverified ·
fe4eb545bbb728e0 - exists helper · level 1 · ran · violated contract ·
aa5486a3650902d8 - linear helper · level 1 · ran · our draft was wrong ·
0e30585f04efffbe - timestep_embedding helper · level 1 · ran; the contract check could not run ·
9df115707ad18735 - zero_module helper · level 1 · ran · our draft was wrong ·
129b804760b3115f - QKVAttention helper · level 1 · ran ·
186bf0385ab93dad - QKVAttentionLegacy helper · level 1 · ran ·
8dd1080ff568f7f4 - checkpoint helper · level 0 · unverified ·
21f94f83ceb82390 - normalization helper · level 1 · ran · our draft was wrong ·
daafc1c89511b8be - avg_pool_nd helper · level 0 · unverified ·
ecd0fc28815b65ae - TimestepBlock helper · level 0 · unverified ·
7958a01675377ce4 - Upsample helper · level 1 · ran ·
1b4579fe4aec5257 - BasicTransformerBlock helper · level 0 · unverified ·
cd763b5f891b0938 - Normalize helper · level 1 · ran · our draft was wrong ·
c3a6b977022957cb - count_flops_attn helper · level 0 · unverified ·
6e9c81a619f204c5 - CheckpointFunction helper · level 1 · ran ·
69360f5b0cc8f069 - GroupNorm32 helper · level 1 · ran ·
426c2385fa431d9a - CrossAttention helper · level 1 · ran ·
edd0dbdde64951f7 - FeedForward helper · level 1 · ran ·
1ce39bf592ba310f - MemoryEfficientCrossAttention helper · level 1 · ran ·
713884729e861c62 - default helper · level 1 · ran · violated contract ·
424012cb37b31172 - max_neg_value helper · level 1 · ran · our draft was wrong ·
f2fe51a4a5646c6f - GEGLU helper · level 1 · ran ·
387673fa5780bf50
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="2404.11474") returns these assemblies with each brick's role and wiring (how to connect).
Tasks
1 archive task tag without a task page not shown.
Results from the paper archive 2025-07-28
No leaderboard rows for this paper in the archive.
Methods
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