Papers › U-VAP: User-specified Visual Appearance Personalization via Decoupled Self Augmentation

U-VAP: User-specified Visual Appearance Personalization via Decoupled Self Augmentation

29 Mar 2024CVPR 2024 1arXiv:2403.20231archive 2025-07-28

You Wu, Kean Liu, Xiaoyue Mi, Fan Tang, Juan Cao, Jintao Li

Concept personalization methods enable large text-to-image models to learn specific subjects (e.g., objects/poses/3D models) and synthesize renditions in new contexts. Given that the image references are highly biased towards visual attributes, state-of-the-art personalization models tend to overfit the whole subject and cannot disentangle visual characteristics in pixel space. In this study, we proposed a more challenging setting, namely fine-grained visual appearance personalization. Different from existing methods, we allow users to provide a sentence describing the desired attributes. A novel decoupled self-augmentation strategy is proposed to generate target-related and non-target samples to learn user-specified visual attributes. These augmented data allow for refining the model's understanding of the target attribute while mitigating the impact of unrelated attributes. At the inference stage, adjustments are conducted on semantic space through the learned target and non-target embeddings to further enhance the disentanglement of target attributes. Extensive experiments on various kinds of visual attributes with SOTA personalization methods show the ability of the proposed method to mimic target visual appearance in novel contexts, thus improving the controllability and flexibility of personalization.

PaperPDFConference PDFCodeCode 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: 7 ran (of which 5 constructed an object rather than computing a result; 6 with no instrument failure: 0 honoured, 0 violated, 6 with no contract checked; 1 where Syntology's instrument failed) · 7 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, 7 ran (6 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-24 (UTC): the dates Syntology's graph wrote each sample's verification level, not when the code executed.

ictmcg/u-vap officialmentioned in papermentioned on GitHubpytorchSyntology: 14 samples, 7 ran (1 instrument-failed) · 7 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: 7 ran (of which 5 constructed an object rather than computing a result; 6 with no instrument failure: 0 honoured, 0 violated, 6 with no contract checked; 1 where Syntology's instrument failed) · 7 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
6ran
7unverified

Licence: 14 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 ictmcg/u-vap. “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 1 sample 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.

ictmcg/u-vap official repository 14 samples, 7 ran (1 instrument-failed) · 7 unverified
CLIPAttention in 5 papers models/modeling_clip.py ran no licence file found · pointer only · 558cf5130888f74c · report fixture: signature hidden_states:Tensor/3/float, attention_mask:NoneType/0/?, causal_attention_mask:NoneType/0/?, output_attentions:bool/0/bool · returned tuple · level recorded 2026-09-24
CLIPOutput in 5 papers models/modeling_clip.py ran no licence file found · pointer only · 58cc0dc08e1bb9df · report fixture: returned CLIPOutput · level recorded 2026-09-22
CLIPTextEmbeddings in 5 papers models/modeling_clip.py ran no licence file found · pointer only · de79008ffa19d769 · report fixture: returned CLIPTextEmbeddings · level recorded 2026-09-22
CLIPTextModelOutput models/modeling_clip.py ran no licence file found · pointer only · 6b93811e04711dd2 · report fixture: returned CLIPTextModelOutput · level recorded 2026-09-22
CLIPVisionEmbeddings in 5 papers models/modeling_clip.py ran no licence file found · pointer only · 4809414b75263882 · report fixture: returned CLIPVisionEmbeddings · level recorded 2026-09-22
CLIPVisionModelOutput models/modeling_clip.py ran no licence file found · pointer only · c0b6d0381e9a60e0 · report fixture: returned CLIPVisionModelOutput · level recorded 2026-09-22
_expand_mask in 13 papers
census: 13 implementations from 13 papers, 2 distinct outputs on one shared input this sample: bucket 1 of 1, arg 1: rank 2, kind float, dtype float32
models/modeling_clip.py ran · our draft was wrong no licence file found · pointer only · 93c6887621a9f47c · report fixture: signature mask:Tensor/2/float, dtype:dtype/0/?, tgt_len:NoneType/0/? · returned Tensor · level recorded 2026-09-22
CLIPEncoder in 6 papers models/modeling_clip.py unverified no licence file found · pointer only · d6ac17c8ddf0f49b · report
CLIPEncoderLayer in 5 papers models/modeling_clip.py unverified no licence file found · pointer only · 6c4ad49ccd8cc6f5 · report
CLIPModel in 6 papers models/modeling_clip.py unverified no licence file found · pointer only · c00b70b4d395e15a · report
CLIPTextModelWithProjection models/modeling_clip.py unverified no licence file found · pointer only · 0a76c5704ab25d88 · report
CLIPTextTransformer in 5 papers models/modeling_clip.py unverified no licence file found · pointer only · fdcf936fbb55bebb · report
CLIPVisionModelWithProjection models/modeling_clip.py unverified no licence file found · pointer only · a922142d0d657e31 · report
CLIPVisionTransformer in 5 papers models/modeling_clip.py unverified no licence file found · pointer only · fa8af7191540e8ef · 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 U-VAP (graph method: U-VAP). 17 bricks; individually on a fixture: 10 ran (of which 6 constructed an object rather than computing a result; 8 with no instrument failure: 1 honoured, 0 violated, 7 with no contract checked; 2 where Syntology's instrument failed) · 7 unverified. The assembly has not been run end-to-end.

  1. CLIPModel entry · level 0 · unverified · c00b70b4d395e15a
  2. CLIPOutput helper · level 1 · ran · 58cc0dc08e1bb9df
  3. CLIPTextTransformer helper · level 0 · unverified · fdcf936fbb55bebb
  4. CLIPVisionTransformer helper · level 0 · unverified · fa8af7191540e8ef
  5. clip_loss loss · level 1 · ran · our draft was wrong · 198ed04eaf39466a
  6. CLIPEncoder helper · level 0 · unverified · d6ac17c8ddf0f49b
  7. CLIPTextEmbeddings helper · level 1 · ran · de79008ffa19d769
  8. _expand_mask helper · level 1 · ran · our draft was wrong · 93c6887621a9f47c
  9. CLIPVisionEmbeddings helper · level 1 · ran · 4809414b75263882
  10. contrastive_loss loss · level 1 · ran · honoured contract · f2e5f28608115fa6
  11. CLIPEncoderLayer model · level 0 · unverified · 6c4ad49ccd8cc6f5
  12. CLIPAttention model · level 1 · ran · 558cf5130888f74c
  13. CLIPMLP model · level 1 · ran · 077b0fff3b85e9e1
  14. CLIPTextModelOutput helper · level 1 · ran · 6b93811e04711dd2
  15. CLIPVisionModelOutput helper · level 1 · ran · c0b6d0381e9a60e0
  16. CLIPTextModelWithProjection helper · level 0 · unverified · 0a76c5704ab25d88
  17. CLIPVisionModelWithProjection helper · level 0 · unverified · a922142d0d657e31

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

Tasks

AttributeDisentanglementSentence

Results from the paper archive 2025-07-28

No leaderboard rows for this paper in the archive.

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